-
Notifications
You must be signed in to change notification settings - Fork 194
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[RFE] consider adding GSI, EMU builds to your buildbot #462
Comments
The Not sure about the emulator builds which seem to involve an extra step, beyond the PS what is '[RFE]'? |
I plan to try a test build of the 20.1 |
request for enhancement, meaning it's really not a bug or issue.
thanks! 18.1 is much more important. i think that GSI 20 builds would mostly work where 19 builds do, as kernels are similar. but neither of those would work with the non-BPF kernels of older devices, so a 18.1 build is important. |
OK. I'll try an 18.1 build |
Adding 'Fix next' label. We'll give this a try when the current build run is complete |
From what I have read, GSI's are useful for Treble-capable devices, which are not yet supported by LOS, possibly because they are too new, which means they are probably running Android 13, and almost certainly Later: So trying to build using Docker failed,
This is not going to be straightforward, and I'm nt interested enough to send much time researching / working out how to build. I'm happy tp receive ideas fromanyone else, but I won;t be following it up myself. Changing label to |
please consider adding LOS20 target
lineage_gsi_arm64
and maybelineage_sdk_phone_x86_64
to your buildbot, for GSI users and emulator users.see: https://wiki.lineageos.org/emulator#start-the-build
thanks!
EDIT: come to think about it, people using GSI builds are probably stuck with older kernels, so a LOS18.1
lineage_arm64
build would also be useful. android 12+ kernels require BPF support, which is the reason why many LOS targets are stuck on LOS18.1 and why the LOS team did not deprecate 18.1.The text was updated successfully, but these errors were encountered: