commit | 0f1b488413703c88e24555859848eeae2d058fdd | [log] [tgz] |
---|---|---|
author | Ankur Bakshi <ankurbakshi@google.com> | Fri Nov 22 20:20:07 2024 +0000 |
committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Fri Nov 22 20:20:07 2024 +0000 |
tree | 3f676ec0499d76f22a49e434febe3aeee64dd012 | |
parent | fa448547d82211c6bd4f6483e3c0342c83c20b4e [diff] | |
parent | 4c4df16ecab0a4443fb543c80ab3dadb3c83c24f [diff] |
Update Security String to 2025-01-01 am: 6c99ed6ee8 am: 73aa60fb4f am: 4c4df16eca Original change: https://googleplex-android-review.googlesource.com/c/platform/build/+/30541109 Change-Id: I0812c987e868f4d0285c8efdd93b1261a8ae58b8 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.