commit | 3a80588af17af24359272a795458337e71ede318 | [log] [tgz] |
---|---|---|
author | Ankur Bakshi <ankurbakshi@google.com> | Wed Jan 08 06:45:10 2025 -0800 |
committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Wed Jan 08 06:45:10 2025 -0800 |
tree | 29a6c9438174c2909985ec2bbc4c42f9c8e25c32 | |
parent | 545cccac230296e70143382c779ed51ffddfa2e4 [diff] | |
parent | e0aca2f0f13068a0541031f51844549616a10c51 [diff] |
Update Security String to 2025-03-01 am: 4db43f45bc am: e0aca2f0f1 Original change: https://googleplex-android-review.googlesource.com/c/platform/build/+/31207471 Change-Id: I07644595ad758b3d74a83e94dd5351b2d890ee33 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.