commit | 6e4c4dadb188ab193508dbc043f7ee8520705217 | [log] [tgz] |
---|---|---|
author | Bassem Khalife <bkhalife@google.com> | Mon Nov 29 23:51:49 2021 +0000 |
committer | Adam Seaton <aseaton@google.com> | Tue Nov 30 18:17:39 2021 +0000 |
tree | 62288827dac9d244b3b91824830bc1cd7324d74e | |
parent | 914c259c94c6bf547e85586b642756989d8660e3 [diff] |
[DO NOT MERGE] Update Security String to 2022-01-01 Bug: 207022948 Change-Id: Id0cffb66a65c60b011d0975ba6b0ff04366472d2 Merged-In: Ie4afce5ae2b2a1b60fb0fc78ea014d220e08a981 Merged-In: Id1ccf89e6cd9e924f9d5c7ca53cdbcd9cd34018b
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.