commit | 4a134c38b2fc62089f725fc0c6f105cd0b51fce6 | [log] [tgz] |
---|---|---|
author | Treehugger Robot <treehugger-gerrit@google.com> | Thu Dec 08 06:20:05 2022 +0000 |
committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Thu Dec 08 06:20:05 2022 +0000 |
tree | fe0718a75493c689ef46644833a298a1b90332b9 | |
parent | 9c3e22139daa120d7087515247df9396af180488 [diff] | |
parent | 77f12153781526cacd81f393aa2b6068b680155a [diff] |
Merge "Almost fully automated finalization." am: 77f1215378 Original change: https://android-review.googlesource.com/c/platform/build/+/2333787 Change-Id: Ia94989f5453627e2e824f6f78a8b4bdab59bf7f4 Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
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.