Gitiles
Code Review Sign In
gerrit.omnirom.org / android_build / 46ab7a55f4873f37baf36ce6f22f4c65caaee05b
commit46ab7a55f4873f37baf36ce6f22f4c65caaee05b[log] [tgz]
authorZiwei Zhang <zhangxh@google.com>Wed Nov 20 04:07:37 2024 +0000
committerAutomerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>Wed Nov 20 04:07:37 2024 +0000
tree58b993230d455b784abbd0b4aa6ea25ed946e432
parenta2fef11e6737575d906f194c8b16bb6409ff07ea [diff]
parent57eedae55ecbd4befa9484819a12cfa4005b23d6 [diff]
Revert^2 "RESTRICT AUTOMERGE: Package xTS console into CTS 13 to support MCTS." am: 8b0499bb9a am: 57eedae55e

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

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