Gitiles
Code Review Sign In
gerrit.omnirom.org / android_build / 16ef5252d968c668379ecb9b5dd4b4788c7ae413
commit16ef5252d968c668379ecb9b5dd4b4788c7ae413[log] [tgz]
authorTongbo Liu <liutongbo@google.com>Thu Oct 10 09:31:29 2024 +0000
committerAutomerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>Thu Oct 10 09:31:29 2024 +0000
tree3a5309ec6c397378575ed452ef0ed5870c7edf26
parentcbd061f34e5ff0e7ee402abb98d07f0378345e4f [diff]
parent792d283fbfeb34de0741e8ef5b38a3d8ce2f0d4e [diff]
[RESTRICT AUTOMERGE] Enable build MCTS on aosp-android13 am: 6468f44329 am: ed35a5f66e am: 792d283fbf

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

Change-Id: I708175fd885cef67fcebe0e5f98ee35b1f4d2f34
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
tree: 3a5309ec6c397378575ed452ef0ed5870c7edf26
  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.