Gitiles
Code Review Sign In
gerrit.omnirom.org / android_build / 0d67032470433eb63abe4b07b04b88d858444f37
commit0d67032470433eb63abe4b07b04b88d858444f37[log] [tgz]
authorZhi Dou <zhidou@google.com>Tue Mar 11 22:12:10 2025 +0000
committerZhi Dou <zhidou@google.com>Tue Mar 11 22:20:15 2025 +0000
tree67953c5f916319a3d4dc0da0c5c5ff999125c5da
parent47f65b9b9f4546496f9ee5ed345d0932a66cd26b [diff]
aconfig:add system_ext in the platform list

system_ext is added back as a separate partition on the device. Missing
it from the list the generated code will use AconfigPackage instead of
the PlatforAconfigPackage to access the flag value.

Test: m com_android_launcher3_flags_lib and check the generated code
uses the right class
Bug: 402133645

Change-Id: Ibc0bce78ec4c540be12f32418d4d241e20aacbc5
1 file changed
tree: 67953c5f916319a3d4dc0da0c5c5ff999125c5da
  1. backported_fixes/
  2. ci/
  3. common/
  4. core/
  5. packaging/
  6. target/
  7. teams/
  8. tests/
  9. tools/
  10. .gitignore
  11. Android.bp
  12. banchanHelp.sh
  13. buildspec.mk.default
  14. Changes.md
  15. CleanSpec.mk
  16. Deprecation.md
  17. envsetup.sh
  18. help.sh
  19. navbar.md
  20. OWNERS
  21. PREUPLOAD.cfg
  22. rbesetup.sh
  23. README.md
  24. shell_utils.sh
  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.