Gitiles
Code Review Sign In
gerrit.omnirom.org / android_build / f00b91522ba32acd2801e0a90d3e3d8432e2a511
commitf00b91522ba32acd2801e0a90d3e3d8432e2a511[log] [tgz]
authorTreehugger Robot <android-test-infra-autosubmit@system.gserviceaccount.com>Mon Nov 06 21:34:37 2023 +0000
committerAutomerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>Mon Nov 06 21:34:37 2023 +0000
treef3ecb2e12027d88a8d736c6837bc375bdb2cc040
parent2e8a41919995fa7bfa6a12098cab527491e71aab [diff]
parent406262c55376e5d001e57e6c0a71b9343194cc6f [diff]
Merge "Add PRODUCT_VALIDATION_CHECKS" into main am: 54e9262f99 am: ca14f7f971 am: 406262c553

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

Change-Id: I8c132fdb86ecd5fbab452799f8fb204d9d84f417
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
tree: f3ecb2e12027d88a8d736c6837bc375bdb2cc040
  1. common/
  2. core/
  3. packaging/
  4. target/
  5. tests/
  6. tools/
  7. .gitignore
  8. banchanHelp.sh
  9. buildspec.mk.default
  10. Changes.md
  11. CleanSpec.mk
  12. cogsetup.sh
  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. shell_utils.sh
  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.