Gitiles
Code Review Sign In
review.blissroms.org / platform_build_make / bb9d6db326ed132dfcb652e3a7de584a52fbe215
commitbb9d6db326ed132dfcb652e3a7de584a52fbe215[log] [tgz]
authorNikita Ioffe <ioffe@google.com>Mon Oct 24 17:21:58 2022 +0100
committerNikita Ioffe <ioffe@google.com>Tue Nov 15 08:40:11 2022 +0000
tree90636fc358c0584096d8664b656de0f7fce88790
parentf0c6cf501c78896a50c53b94cdf9370c6623fa07 [diff]
Unconditionally install com.android.virt APEX

The change in the packages/modules/Virtualization in the same topic
takes care for defining the right variant of the APEX to be installed:

* Devices with AVF support will get the full com.android.virt APEX
* Devices without AVF support will get an almost empty version that only
  contains an app that defines AVF-related permissions, and soon the BCP
  fragment jar.

Bug: 243512044
Test: build & flash oriole
Test: build & flash redfin
Change-Id: I2c38e03529a77dd2820212812433741725115ce0
3 files changed
tree: 90636fc358c0584096d8664b656de0f7fce88790
  1. common/
  2. core/
  3. packaging/
  4. target/
  5. tests/
  6. tools/
  7. .gitignore
  8. banchanHelp.sh
  9. buildspec.mk.default
  10. Changes.md
  11. CleanSpec.mk
  12. Deprecation.md
  13. envsetup.sh
  14. finalize-aidl-vndk-sdk-resources.sh
  15. finalize-cleanup.sh
  16. finalize-step-1.sh
  17. finalize_branch_for_release.sh
  18. help.sh
  19. METADATA
  20. navbar.md
  21. OWNERS
  22. PREUPLOAD.cfg
  23. rbesetup.sh
  24. README.md
  25. tapasHelp.sh
  26. Usage.txt
README.md

Android Make Build System

This is the Makefile-based portion of the Android Build System.

For documentation on how to run a build, see Usage.txt

For a list of behavioral changes useful for Android.mk writers see Changes.md

For an outdated reference on Android.mk files, see build-system.html. Our Android.mk files look similar, but are entirely different from the Android.mk files used by the NDK build system. When searching for documentation elsewhere, ensure that it is for the platform build system -- most are not.

This Makefile-based system is in the process of being replaced with Soong, a new build system written in Go. During the transition, all of these makefiles are read by Kati, and generate a ninja file instead of being executed directly. That's combined with a ninja file read by Soong so that the build graph of the two systems can be combined and run as one.