commit | d5818bad5eeffe9ee95b5b815a07aedc7f333773 | [log] [tgz] |
---|---|---|
author | Ankur Bakshi <ankurbakshi@google.com> | Thu Feb 01 19:38:12 2024 +0000 |
committer | Ankur Bakshi <ankurbakshi@google.com> | Thu Feb 01 19:43:06 2024 +0000 |
tree | bdd066311e8bf2ddc0124f555f00262b972bf777 | |
parent | a396e3bce95bcdb603dd7e0d9fcc834b3e14b104 [diff] |
Update Security String to 2024-03-01 Bug: 313797924 Change-Id: Ie419865a7b5ee09a7fff77d1e3c0127f1380426a Merged-In: Ie419865a7b5ee09a7fff77d1e3c0127f1380426a Merged-In: I52d82f4024dd3ec332d0ab2d13b72301c667c29e Merged-In: Ib648c3046c0ef70684b547fa97535fa73d7656bb Merged-In: I9edc7171d124f0cfa540fea6f0e06ba877910444
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.