Gitiles
Code Review Sign In
gerrit.omnirom.org / android_build / 792d283fbfeb34de0741e8ef5b38a3d8ce2f0d4e
commit792d283fbfeb34de0741e8ef5b38a3d8ce2f0d4e[log] [tgz]
authorTongbo Liu <liutongbo@google.com>Thu Oct 10 08:49:51 2024 +0000
committerAutomerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>Thu Oct 10 08:49:51 2024 +0000
treef11a28cd0923c21ddd0a83aa9f4407240d637643
parent1af309527a8bdc2ca87b14096309184df09fb880 [diff]
parented35a5f66e52ca997e3a2b3f2e488f69ae398442 [diff]
[RESTRICT AUTOMERGE] Enable build MCTS on aosp-android13 am: 6468f44329 am: ed35a5f66e

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

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