commit | d14ff203d4ddd102eb80dde1baad44c2072ae047 | [log] [tgz] |
---|---|---|
author | Ankur Bakshi <ankurbakshi@google.com> | Thu Feb 01 22:44:39 2024 +0000 |
committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Thu Feb 01 22:44:39 2024 +0000 |
tree | 74ec7a5fa67088fe391462633cec17db1d0f4f1f | |
parent | 1ad105c0fa595411d31e48a6194d36fbd225c1ba [diff] | |
parent | 8ee61b4ba96077f85f4ae14581dfec78fcc4dcc2 [diff] |
Update Security String to 2024-02-01 am: a396e3bce9 am: 12b5c15899 am: 680d85b56a am: 2007bbcfe9 am: 8ee61b4ba9 Original change: https://googleplex-android-review.googlesource.com/c/platform/build/+/25498991 Change-Id: I47f1c1d5b05a6f7841a3e74d8761ec57d21d8ee3 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.