commit | fafba401d3b83a6f506ad37f80b19a9df6ff5410 | [log] [tgz] |
---|---|---|
author | Bill Yi <byi@google.com> | Tue Nov 08 22:25:51 2022 -0800 |
committer | Bill Yi <byi@google.com> | Tue Nov 08 22:26:15 2022 -0800 |
tree | 3730cb31d303f341c93f564ce3436f952ebd1e27 | |
parent | afeadc35616ba44e52beea72016d3029bf8619fd [diff] | |
parent | 9de99946edf0941d56dcb8f3bf6ed948669a3a44 [diff] |
Merge TP1A.221105.002 to aosp-master - DO NOT MERGE Merged-In: I760ad49579961037628fde4d0300644aa2f6c188 Merged-In: I4e94edbf42259eedb96e46d85b46c2d336f59d75 Merged-In: I4e94edbf42259eedb96e46d85b46c2d336f59d75 Change-Id: I453b1617db1973432e2745718ec3e3c86cd933e6
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.