Gitiles
Code Review Sign In
review.blissroms.org / platform_build_make / ad24fc0ed537c5c51a8136ff6530d93a5e8dbb95
commitad24fc0ed537c5c51a8136ff6530d93a5e8dbb95[log] [tgz]
authorBassem Khalife <bkhalife@google.com>Tue Nov 30 23:18:56 2021 +0000
committerAutomerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>Tue Nov 30 23:18:56 2021 +0000
tree2fd4f182478d51c8355d242aa4087afb1a979dff
parent4877c95bec5d60d2a5701df402229d2bdeaa4672 [diff]
parent6e4c4dadb188ab193508dbc043f7ee8520705217 [diff]
[automerger skipped] [DO NOT MERGE] Update Security String to 2022-01-01 am: 6e4c4dadb1 -s ours

am skip reason: Merged-In Ie4afce5ae2b2a1b60fb0fc78ea014d220e08a981 with SHA-1 9e20227ea5 is already in history

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

Change-Id: I91b37a03d55c2bbf2b811d363bc01f5fdf800360
tree: 2fd4f182478d51c8355d242aa4087afb1a979dff
  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.