| commit | a396e3bce95bcdb603dd7e0d9fcc834b3e14b104 | [log] [tgz] |
|---|---|---|
| author | Ankur Bakshi <ankurbakshi@google.com> | Wed Nov 29 07:29:43 2023 +0000 |
| committer | Lokesh Kumar Goel <lokeshgoel@google.com> | Thu Feb 01 17:40:56 2024 +0000 |
| tree | b4dc88ac17e98eb62de157e478be011358b0e928 | |
| parent | 4ac29fff9927bf64afb686597928d514f40d4cd7 [diff] |
Update Security String to 2024-02-01 Bug: 313696499 Change-Id: Ibf217f5d11fd16ef03730311fdd0816a276f7135 Merged-In: Ibf217f5d11fd16ef03730311fdd0816a276f7135 Merged-In: I6270b75c2a5aff6daa8dc483dedc82b6f93f9161 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.