I would install the tools on your boot drive, then use the big drive for your working directories.
Create a working directory on the big drive. If you are building with Docker or the picomatic builde.sh script, you use the -v parameters to use that as the root directory. If you are building the traditional way, then start in that directory (or a subdirectory) when you do the initial repo sync.
450GB should give you space to have at least two separate source trees (e.g. one Q, one Android 11, or one /e/ and one LineageOS or Linegageos4microG).
PS I have a Building /e/ ROMs - a Beginner's Guide wiki page that you may find useful
It’s all a bit confusing for a first timer, so I greatly appreciate your help. Your beginners tips is very informative.
I have a Google Pixel 3 XL, which currently is not on the official, nor custom, nor unofficial lists. But it looks like a possiblity exists since the Pixel 3XL is compatible with Project Treble.
Continuing on with efoundation posts, here’s a Pixel 3a XL inquiry regarding GSI:
h t t p s : / / community.e.foundation/t/howto-install-eos-gsi-on-a-treble-device-new-gsi-added-june-14th/14898/12
And this:
h t t p : / / community.e.foundation/t/gsi-for-not-yet-supported-treble-phones-2020-06-14/6412
. . .
For the Google Pixel 3 XL, I’m not quite sure how next to proceed. It seems all roads point to using GSI source.
I’ve currently got the Scorpion custom recovery and ROM on the Google Pixel 3 XL.
If you have any further suggestions, I would appreciate it.
Also regarding what you wrote in your beginner’s tips about using the cloud and picomatic, that may be a route that I could also try along with my low-ram local computer.
I don’t think that I can use docker on my vps since I’m running the Virtualmin control panel and I don’t the two play nicely together (but could be totally wrong about that).
It looks like there is an official build of LineageOS 17.1 for this device, (See https://download.lineageos.org/crosshatch and https://wiki.lineageos.org/devices/crosshatch/) so it should be really straightforward to build an /e/ ROM. I think you just need to put the device name crosshatch into the build command, and set the INCLUDE_PROPRIETARY environment variable to true.
I think I was mistaken in thinking that you wanted me to build with Lineage17.1. I went ahead with Lineage 17.1 and I can’t get pass some build errors. Rather, I think because Lineage17.1 could work for the Pixel 3 XL, you wanted to suggest that it would be easy to build /e/ for the Pixel 3 XL.
[ 99% 634/635] finishing build rules …
FAILED:
hardware/qcom/sdm845/bt/libbt-vendor/Android.mk: error: “libbt-vendor (SHARED_LIBRARIES android-arm64) missing libbtnv (SHARED_LIBRARIES android-arm64)”
You can set ALLOW_MISSING_DEPENDENCIES=true in your environment if this is intentional, but that may defer real problems until later in the build.
hardware/qcom/sdm845/bt/libbt-vendor/Android.mk: error: “libbt-vendor (SHARED_LIBRARIES android-arm) missing libbtnv (SHARED_LIBRARIES android-arm)”
You can set ALLOW_MISSING_DEPENDENCIES=true in your environment if this is intentional, but that may defer real problems until later in the build.
hardware/qcom/sdm845/media/mm-video-v4l2/vidc/venc/Android.mk: error: “libOmxSwVencMpeg4 (SHARED_LIBRARIES android-arm64) missing libMpeg4SwEncoder (SHARED_LIBRARIES android-arm64)”
You can set ALLOW_MISSING_DEPENDENCIES=true in your environment if this is intentional, but that may defer real problems until later in the build.
hardware/qcom/sdm845/media/mm-video-v4l2/vidc/venc/Android.mk: error: “libOmxSwVencMpeg4 (SHARED_LIBRARIES android-arm) missing libMpeg4SwEncoder (SHARED_LIBRARIES android-arm)”
You can set ALLOW_MISSING_DEPENDENCIES=true in your environment if this is intentional, but that may defer real problems until later in the build.
build/make/core/main.mk:972: error: exiting from previous errors.
22:10:32 ckati failed with: exit status 1
failed to build some targets (21:03 (mm:ss))
root@peace:/home/lineage#
. . .
I thought it might be due to not having the vendor proprietary blobs so I went through the process of unzipping Lineage17.1 and using the extract-files.sh script. It unzipped boot/system/vendor.img out of payload.bin, but it didn’t populate the vendor/google folder (there wasn’t one). Same build failures, so no success there.
…
Anyways, I’m stuck at this point with Lineage 17.1
That is correct I meant that you should try building /e/
[ 99% 634/635] finishing build rules …
FAILED:
hardware/qcom/sdm845/bt/libbt-vendor/Android.mk: error: “libbt-vendor (SHARED_LIBRARIES android-arm64) missing libbtnv (SHARED_LIBRARIES android-arm64)”
You can set ALLOW_MISSING_DEPENDENCIES=true in your environment if this is intentional, but that may defer real problems until later in the build.
[/quote]
I imagine you will get the same error in your /e/ build. If so, then try setting this ALLOW_MISSING_DEPENDENCIES environment variable and see if it builds OK.