Gitiles
Code Review Sign In
gerrit.omnirom.org / android_build / 23265631b242a4b45be68b954e4b352e9683ddfb
commit23265631b242a4b45be68b954e4b352e9683ddfb[log] [tgz]
authorTreehugger Robot <android-test-infra-autosubmit@system.gserviceaccount.com>Tue Jan 23 05:12:00 2024 +0000
committerAutomerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>Tue Jan 23 05:12:00 2024 +0000
tree2447e8a722408f8207de48e40d61b949cc0a9233
parentc917c46314f3b4682995ad75f003e02c68e43a08 [diff]
parent04acb6d25584b7ee42617bf998903bd768b2209b [diff]
Merge "Use RELEASE_BOARD_API_LEVEL_FROZEN" into main am: 04acb6d255

Original change: https://android-review.googlesource.com/c/platform/build/+/2919149

Change-Id: I33f48fb9f73eb6b5159d3f6cec0e021848a4377a
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
tree: 2447e8a722408f8207de48e40d61b949cc0a9233
  1. ci/
  2. common/
  3. core/
  4. packaging/
  5. target/
  6. tests/
  7. tools/
  8. .gitignore
  9. banchanHelp.sh
  10. buildspec.mk.default
  11. Changes.md
  12. CleanSpec.mk
  13. cogsetup.sh
  14. Deprecation.md
  15. envsetup.sh
  16. help.sh
  17. METADATA
  18. navbar.md
  19. OWNERS
  20. PREUPLOAD.cfg
  21. rbesetup.sh
  22. README.md
  23. shell_utils.sh
  24. tapasHelp.sh
  25. 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.