commit | 52724e91ffa3622ab38be3ee184e0ab770d8ec39 | [log] [tgz] |
---|---|---|
author | Ankur Bakshi <ankurbakshi@google.com> | Wed Feb 14 21:18:59 2024 +0000 |
committer | Ankur Bakshi <ankurbakshi@google.com> | Wed Feb 14 21:20:49 2024 +0000 |
tree | 025345182b2cf2d28b0a05433d6fe2db43d4a4fc | |
parent | 025ca884e77f20f7162465283056de847550996a [diff] |
Update Security String to 2024-04-01 Bug: 325156176 Change-Id: I789fcbffc56a3ca73697ff1e0268fe862c80f2de Merged-In: I789fcbffc56a3ca73697ff1e0268fe862c80f2de Merged-In: Id8d88a3a27730910e0b8b099dada0f31c0a14ba8 Merged-In: If81222f13727b8a2c8faf1c685d917ee4697c903 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.