Google Git
Sign in
android / platform / build / 47ce0c5e1b4bb9d5e451b37a1166cb63e5ef7689
commit47ce0c5e1b4bb9d5e451b37a1166cb63e5ef7689[log] [tgz]
authorTreeHugger Robot <treehugger-gerrit@google.com>Fri Jul 16 21:56:59 2021 +0000
committerAutomerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>Fri Jul 16 21:56:59 2021 +0000
treecb3eebd8bc105153f6bfbf3b79f4e23e65ed1f8c
parente5f0b9f66e15e05a0ab09c8f5870dfeb66ffc7a9 [diff]
parent9bbb60e14100070e284ccb2fda1891b2e4ec28ac [diff]
[automerger skipped] Merge changes from topic "ota_for_generic_boot_image" into sc-dev am: 9bbb60e141 -s ours

am skip reason: Merged-In I43dd8e206bcd1c9f3f5f51869f126791c50af01a with SHA-1 b1627779fb is already in history

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

Change-Id: Ic1700a13cb5e765523cd470c7fee2bcdd7fc0c52
tree: cb3eebd8bc105153f6bfbf3b79f4e23e65ed1f8c
  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.