Thanks! I think that makes more sense than the docker way indeed.
Cool! Just to make sure I understand correctly, you’ve built /e/ for a device (if so, which one?) and at the end the process output had also the emulator system images? One question that pops into my mind is that ideally the emulator images would be x86_64, whereas the device images are usually arm64.
Yes, just a limited functionality device to test apps, just like Google’s distribution. Nothing fancier for now.
You are well ahead of me on the detail, I was talking in general terms; like I see in /prebuilts/android-emulator/ (this is stuff ready to use, “stock” as it were)
darwin-x86_64
linux-x86_64
update_emulator.sh
and on the output side of things in /build/make/target/product/ (ready to be used by build instructions)
I managed to start the emulator images building on lineageos4microg, but I got stuck at this error:
FAILED: ninja: ‘external/chromium-webview/prebuilt/x86_64/webview.apk’, needed by ‘out/target/product/emulator_x86_64/obj/APPS/webview_intermediates/package.apk’, missing and no known rule to make it
Before going down another rabbit hole trying to fix this, I’ll try the /e/ build with the same settings.
It looks from here as if you now have two rabbit holes pointing (loosely) to repo (sync) errors.
In my experience docker will carry on with a build without ensuring “repo sync complete”
Did you check if external/chromium-webview/prebuilt/x86_64/webview.apk exists in your build environment? Are you building in Q or R?
I find that external/chromium-webview/prebuilt/x86_64/webview.apk exists in Q – but also a fairly complicated external/chromium-webview/README which looks pertinent to your emulator.
I have tried multiple versions, including R. But fist of all I have to admit that I’ve been lazy and trying to get an emulator image as “cheaply” as possible without going through the process of understanding what is happening, neither following on the errors too much. I just hoped I would get away with just trying a few build configurations randomly. I know this is quite wrong!
In any case, I did make some progress.
I’ve built a docker image (tagged as myeos) using this repo.
The animation works fine, but the system doesn’t go beyond this atm. As seen in the background, QEMU system is full on busy, but the boot doesn’t go any further than this.
One thing that I don’t understand and appreciate clarification on is the /e/ OS docker image. I have build my own docker image from this repo because it had some emulator references. But the official /e/ OS docker image called
Url is registry.gitlab.e.foundation/e/os/docker-lineage-cicd:community, seems pretty familiar to me
NB : you can forget the :5000 thing, as registry is also available though HTTPS (443).