Gitiles
Code Review Sign In
review.blissroms.org / platform_build_make / b94c00eed2d834c84c82ae982b913f22cdab07a4
commitb94c00eed2d834c84c82ae982b913f22cdab07a4[log] [tgz]
authorsatayev <satayev@google.com>Thu May 06 14:11:42 2021 +0000
committerAutomerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>Thu May 06 14:11:42 2021 +0000
treef8bd858983a74a89e99480d4d0cedfa464921d7e
parent897953f771da2609ec965cd36ce7ff64a6d35f13 [diff]
parenteb33b7b8b7ef58feddf9e60c6767e9d57b6c2d24 [diff]
[automerger skipped] Merge "Sort PRODUCT_UPDATABLE_BOOT_JARS." am: 870137625e am: 96b680d8c7 am: 88a2036210 -s ours am: eb33b7b8b7 -s ours

am skip reason: Merged-In I15512c0da79ad94b547325d563dac473c006f9fd with SHA-1 9425daba0c is already in history

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

Change-Id: I613863c2ca808cf3379ff2f45331b96869016183
tree: f8bd858983a74a89e99480d4d0cedfa464921d7e
  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.