|author||Steve Berbary <firstname.lastname@example.org>||Fri Sep 09 19:25:14 2022 +0000|
|committer||Android Build Coastguard Worker <email@example.com>||Wed Sep 14 17:51:59 2022 +0000|
Update Security String to 2022-11-05 Bug: 244460991 Change-Id: If6c0dc2d69b70f9722da0950582aa5acf224c0fe (cherry picked from commit 831521e2fef74aba45d27eab3d92a60718f4ae2f) Merged-In: If6c0dc2d69b70f9722da0950582aa5acf224c0fe
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.