commit | 7722de1a8925c57c08324ee68b92fa9f969500f4 | [log] [tgz] |
---|---|---|
author | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Thu Feb 06 10:09:44 2025 -0800 |
committer | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Thu Feb 06 10:09:44 2025 -0800 |
tree | c83de9633f795fe121874e69d03aa468c25b4b26 | |
parent | 95369785d3253236f34c9cb296baff9b729d42fa [diff] | |
parent | 7b5cbd8efdaaece79cc9667d84a3060d3da3f134 [diff] |
[coastguard skipped] Merge sparse cherrypicks from sparse-13009785-L68500030009402311 into 25Q1-release. COASTGUARD_SKIP: Ibd82092054dec0d7ee8da9cfd535bba9852bef54 Change-Id: Ic85d5ea8cf068a10ed88503edc9f17c91140bb8f
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.