commit | 5d3aa38bbda73f3152827c317e185bc379c2751e | [log] [tgz] |
---|---|---|
author | Robin Peng <robinpeng@google.com> | Tue Jun 28 11:10:56 2022 +0800 |
committer | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Thu Jul 07 01:45:59 2022 +0000 |
tree | 37e33f73286703886f4e568f862a64d57f488776 | |
parent | 13bdb8eeaf240446b038212ab3ada95fe85e9e52 [diff] |
Update Security String to 2022-06-01 Bug: 237343008 Change-Id: Idcf191ce2b604424eb8b7d8f777dcd693e77c9df (cherry picked from commit 222fbedf7dba37d3217c466ff5c8f425e65a9fb0) Merged-In: Idcf191ce2b604424eb8b7d8f777dcd693e77c9df
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.