OK, will try …
works on Ubuntu 18.04
build completed successfully (25:40 (mm:ss))
yes, on my laptop with Ubuntu 18.04 it’s also compiling now. But it will need longer because of USB HD
1 Like
I would like to try building a GSI, but it will need to be on a cloud compute instance as my home setup isn’t up to Android builds yet. The instance will be Ubunbtu 18.04, with all recent updates applied.
Is this process likely to be feasible in that environment? Clearly I will need repo and git installed. Is there any thing else I need to setup, or will the buildbot.sh script pull in everything I need?
This script will do everything. https://ecloud.global/s/wJiLRcbw2oSmy42
But you have to edit the treble_build_los/buildbot_treble.sh. You have to decide which buildvariant you need. make the others as a comment.
Have you seen that I have created eOS Q GSI (Android 10) ?
I got errors with repo init -u https://gitlab.e.foundation/e/os/releases.git -b refs/tags/v1-pie
Tried instead with ...-b refs/tags/v0.9.4-pie and the the repo sync is running. I’ll go and make my lunch while it completes 
1 Like
The buildbot_treble.sh script is running, and I’m seeing this message many times, but the script continues to run. Is this normal?
fatal: Resolve operation not in progress, we are not resuming.
error: no cherry-pick or revert in progress
fatal: revert failed
fatal: Resolve operation not in progress, we are not resuming.
Doesn’t look like good news!
That’s because “v1-pie” is a branch and not a tag so you have to remove the “refs/tags/”.
OK. I’ll carry on with the v0.9.4-pie tag for now and see what happens
Have you started with an empty source folder? Better you will make a complete fresh start
So rm -rf * in my working directory, then start from repo init…`?
Or will repo init.. and `repo sync… amount to the same thing?
best rm -rf (I do it with my file explorer 
)
Started again from scratch. Woking with -b v1-pie
Seeing lots of these messages
fatal: Resolve operation not in progress, we are not resuming.
error: no cherry-pick or revert in progress
fatal: revert failed
but the script continues to run. Is this normal?
As far as I remember (my last build is 2 month ago) Yes. There are some files which are patched in the los souces.
And after 34 minutes, the script fails…
Applying GSI-specific patches
Applying: Revert "Enable dyanmic image size for GSI"
[detached HEAD 527ef96] Revert "tinycompress: Use generated kernel headers"
Date: Wed Aug 5 15:12:32 2020 +0000
1 file changed, 1 insertion(+), 1 deletion(-)
fatal: previous rebase directory .git/rebase-apply still exists but mbox given.
rm: cannot remove 'vendor/qcom/opensource/cryptfs_hw': Is a directory
fatal: not a git repository (or any parent up to mount point /)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
fatal: not a git repository (or any parent up to mount point /)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
CHECK PATCH STATUS NOW!
Couldn't locate the top of the tree. Try setting TOP.
build/envsetup.sh: line 645: vendor/lineage/build/tools/roomservice.py: No such file or directory
cat: /build/envsetup.sh: No such file or directory
cat: /vendor/lineage/build/envsetup.sh: No such file or directory
cat: /build/envsetup.sh: No such file or directory
cat: /vendor/lineage/build/envsetup.sh: No such file or directory
build/envsetup.sh: line 64: build/soong/soong_ui.bash: No such file or directory
** Don't have a product spec for: 'lineage_treble_a64_aeN'
** Do you have the right repo manifest?
build/envsetup.sh: line 1603: make: command not found
#### failed to build some targets ####
mv: cannot stat 'system.img': No such file or directory
treble_build_los/buildbot_treble.sh: line 107: zip: command not found
treble_build_los/buildbot_treble.sh: line 123: cd: vendor/lineage: No such file or directory
fatal: not a git repository (or any of the parent directories): .git
Buildbot completed in 34 minutes and 24 seconds
And that’s me done for today. The weather has improved so I’m off to do something outside. I’ll decide tomorrow whether to come back to this, or to build an up-to-date unofficial (non-GSI) ROM
there is something wrong with the sources.
Never seen such an error before 
I would prefer that you will run a ‘repo sync --force-sync’ direct from terminal.
You will get some sync errors. delete the folders and run sync once more.
If the sync finish successful run from root source folder
‘treble_build_los/buildbot_treble.sh’
That’s what I did. I ran the commands that are in your script manually in the terminal. In this case they were
repo init -u https://gitlab.e.foundation/e/os/releases.git -b v1-pie
git clone https://github.com/MyOxy/e_gsi_localmanifest .repo/local_manifest
repo sync -j4 --force-sync
nano treble_build_los/buildbot_treble.sh # to choose which variant to build
bash treble_build_los/buildbot_treble.sh
mhm, not really sure how I can help.
In .repo/local_manifests you have a ‘manifest.GSI.xml’, right ?
and in your source tree you have 3 special folders
- treble_build_los
- treble_experimentations
- teble_patches
in /vendor you have the folder - hardware_overlay
- interfaces
- vdnk
- vdnk-test
in /device you have the folder - phh
If yes, The buildbot should work. I can check it here, but that will need time, because I’m still on Q-GSI building
Don’t worry - I’ll try to figure it out. (It’s started raining again)
The script is failing to apply a patch in the vendor/lineage repo. My git knowledge is a bit old, but I’ll see if I can get past it
Thanks for your help