| commit | 6b7cdc58477c6b7d9d9d6178bb48dbb0643d60a3 | [log] [tgz] |
|---|---|---|
| author | Steve Berbary <sberbary@google.com> | Mon Mar 14 18:02:35 2022 +0000 |
| committer | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Mon Mar 21 17:07:44 2022 +0000 |
| tree | 2a7514090a2bd65a5efe60ecc386736c7df6c2d2 | |
| parent | 40903c6d377c9b1485381f79aa7ddfd4ba77dd0f [diff] |
Update Security String to 2022-05-01 Bug: 223313197 Change-Id: I5a35451e14cba5f115ab66926d62c4fa4556a267 Merged-In: I5a35451e14cba5f115ab66926d62c4fa4556a267 (cherry picked from commit 8f3602319f14f9b4d23ed4494700e43ee736e54b) Merged-In: I5a35451e14cba5f115ab66926d62c4fa4556a267
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.