Gitiles
Code Review Sign In
gerrit.omnirom.org / android_build / 49377db572f9b6d7a4d0dc1dc25d531753b6549b
commit49377db572f9b6d7a4d0dc1dc25d531753b6549b[log] [tgz]
authorJiakai Zhang <jiakaiz@google.com>Wed Dec 22 13:38:17 2021 +0000
committerJiakai Zhang <jiakaiz@google.com>Wed Dec 22 13:38:17 2021 +0000
tree630ebbaf0377423bd2668faa4d0dacd27234b9ee
parentf6e4b7b769052f38f8ca33a660aba07e7f410aaa [diff]
Update comments for Makefile variables about APEX jars.

Modules available in Q should not add new entries to
PRODUCT_APEX_*_JARS. Otherwise, there will be problems when a Q device
gets new modules and then OTAs to S, in which case, the device will have
the S version of SdkExtension (because SdkExtension is not available in
Q, see go/mainline-ota-problem), and the S version of SdkExtension
cannot consume those new entries correctly.

Bug: 203198541
Test: N/A
Change-Id: I15367ca59a06b4ee5fdb3803f2e4615b5d03b458
1 file changed
tree: 630ebbaf0377423bd2668faa4d0dacd27234b9ee
  1. common/
  2. core/
  3. packaging/
  4. target/
  5. tests/
  6. tools/
  7. .gitignore
  8. Android.bp
  9. banchanHelp.sh
  10. buildspec.mk.default
  11. Changes.md
  12. CleanSpec.mk
  13. Deprecation.md
  14. envsetup.sh
  15. help.sh
  16. METADATA
  17. navbar.md
  18. OWNERS
  19. PREUPLOAD.cfg
  20. rbesetup.sh
  21. README.md
  22. tapasHelp.sh
  23. 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.