Google Git
Sign in
android / platform / build / refs/heads/android15-platform-release
commit2e41d6e81290e0e271c5c32fc3df2bb0ada82c46[log] [tgz]
authorAndroid Build Coastguard Worker <[email protected]>Sun Dec 22 21:03:04 2024 -0800
committerAndroid Build Coastguard Worker <[email protected]>Sun Dec 22 21:03:31 2024 -0800
treeea6c317ae00019c58a2210275dc24e667e9cc990
parent1fa4ac9ba73a1e407fbc030ca1f50ca05621cf49 [diff]
parenta276477e0bcae7e3420703acd442783e3b029ede [diff]
Make change and version bump to APM1.240918.012
Merge cherrypicks of ['googleplex-android-review.googlesource.com/30943323', 'googleplex-android-review.googlesource.com/31011138'] into 24Q3-platform-release.

Change-Id: I67e89590a3c68c4a18be36159da0357337ea9486
tree: ea6c317ae00019c58a2210275dc24e667e9cc990
  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. cogsetup.sh
  17. Deprecation.md
  18. envsetup.sh
  19. help.sh
  20. navbar.md
  21. OWNERS
  22. PREUPLOAD.cfg
  23. rbesetup.sh
  24. README.md
  25. shell_utils.sh
  26. tapasHelp.sh
  27. 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.