| commit | 398ff1a8b603e01c67725b1209ab67907cdba284 | [log] [tgz] |
|---|---|---|
| author | Steve Berbary <sberbary@google.com> | Wed Dec 07 19:17:20 2022 +0000 |
| committer | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Wed Dec 14 02:23:24 2022 +0000 |
| tree | 0d06e2d678b007eabb3107f002cccf21fb7e0bad | |
| parent | ce74932aa9a84a00bcef1de95915ba3938499d82 [diff] |
Update Security String to 2023-02-05 Bug: 261738635 Change-Id: Ifcca8fadc558099b223a39e8b2f98bcb8db40c6f (cherry picked from commit 79e595f4e3f7015c9911436d449ee7dd8fa87982) Merged-In: Ifcca8fadc558099b223a39e8b2f98bcb8db40c6f
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.