commit | 877ca9f537c1253885582f3ddb87a22dd4316be3 | [log] [tgz] |
---|---|---|
author | Steve Berbary <sberbary@google.com> | Tue Mar 14 04:30:17 2023 +0000 |
committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Tue Mar 14 04:30:17 2023 +0000 |
tree | 00aa3a12aab21b06109172670eb474fe5d7690f7 | |
parent | 4fa3bcc635cc1550880fb77486b8072ad95b27ee [diff] | |
parent | 24272b1f7eceb8caacd594c42268bdd2aadd4992 [diff] |
Update Security String to 2023-05-01 am: 2130534b73 am: 24272b1f7e Original change: https://googleplex-android-review.googlesource.com/c/platform/build/+/21960115 Change-Id: I9a6f1a6d9be4978dd534f4e409fa864d4b68b48a Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
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.