7d91c1b33c
* Use device as an identifier in package names so APEXs on rpi4/rpi5 trees can co-exist. Somehow apex definitions escape the soong namespace. It doesn't complain about duplicate package names but dependecies later in the build after analyzing Android.bp files and generating ninja file. FAILED: ninja: ... multiple rules generate com.android.hardware.bluetooth.rpi-deps-info [-w dupbuild=err] https://android.googlesource.com/platform/build/soong/+/refs/heads/main/README.md#namespaces * Not sure if this is an AOSP bug or intended behaviour for apex targets. Don't like using the rpi4/rpi5 tags but couldn't come up with better solution to limit the visibility that worked. * General cleanups. As APEX package contains all dependencies that are needed for the service, remove unused shared libraries. Run 'bpfmt -s -w Android.bp'.
Raspberry Vanilla AOSP 15 device configuration for Raspberry Pi 4.