commit | cb105c802276677d1a492f662f05a9a39114462e | [log] [tgz] |
---|---|---|
author | Steve Berbary <sberbary@google.com> | Wed Nov 09 18:12:40 2022 +0000 |
committer | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Wed Nov 09 18:26:36 2022 +0000 |
tree | dfa58768b3335cf4cb21b6a4ec80cc23cf20d3ce | |
parent | c711789164937a702ae8bd3a7f49f4dcf2f81074 [diff] |
Update Security String to 2022-12-01 Bug: 250644806 Change-Id: I79e50fe61a3b5c4c269625113802db578525fb26 (cherry picked from commit a94ddc8f0e5ce5dad63f0832301ef1513f149939) Merged-In: I79e50fe61a3b5c4c269625113802db578525fb26
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.