Gitiles
Code Review Sign In
review.blissroms.org / platform_build_make / 14cf8d494fa483a4419940207d4a4be0174e19af
commit14cf8d494fa483a4419940207d4a4be0174e19af[log] [tgz]
authorColin Cross <ccross@android.com>Wed Sep 29 17:13:23 2021 +0000
committerAutomerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>Wed Sep 29 17:13:23 2021 +0000
treeb226a901cde1403e025d678c23df3730cdb91e2c
parent6487d1dfd74ae28ca7c6a4eae6ca2d224f91e559 [diff]
parent2b595c26d14e3f408f71efbcf67741c86f3b04b2 [diff]
[automerger skipped] Merge "Update build_id.mk and version_defaults.mk for SC QPR1" into sc-qpr1-dev am: 2b595c26d1 -s ours

am skip reason: Merged-In Ie8bed4cefed83db5324ad98b6e70cb69b3f82780 with SHA-1 6487d1dfd7 is already in history

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

Change-Id: I43e19d61b2f5e7181bcb7f7406fe1fcb78b6474c
tree: b226a901cde1403e025d678c23df3730cdb91e2c
  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.