commit | 4ac29fff9927bf64afb686597928d514f40d4cd7 | [log] [tgz] |
---|---|---|
author | Ankur Bakshi <ankurbakshi@google.com> | Tue Nov 07 04:34:28 2023 +0000 |
committer | Bassem Khalife <bkhalife@google.com> | Fri Nov 17 03:05:31 2023 +0000 |
tree | f1bf3365ad70233c8d2a70576df146d7fcef12f9 | |
parent | c2b45030ce9878bca612410b019b9f7fe1e7211e [diff] |
Update Security String to 2024-01-01 Bug: 309529736 Change-Id: I4fd1cbb419bb5d84ebe33779823061695b10c89d Merged-In: I4fd1cbb419bb5d84ebe33779823061695b10c89d Merged-In: I9edc7171d124f0cfa540fea6f0e06ba877910444 Ignore-AOSP-First: Internal first as its needed for preparing the release
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.