commit | a3cbafe0fa617649ba94b855f54218399b8b65e5 | [log] [tgz] |
---|---|---|
author | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Tue Mar 25 15:08:19 2025 -0700 |
committer | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Tue Mar 25 15:08:19 2025 -0700 |
tree | 56d8dba2bdecc31398b3a708ae5c6a9a608d05c6 | |
parent | b57a80be5c2578dff0ed334489928cff765c3b42 [diff] | |
parent | c5ef8f4737c5c685ff57631a5142b31257790ee8 [diff] |
[coastguard skipped] Merge sparse cherrypicks from sparse-13270399-L13500030010685594 into 25Q1-release. COASTGUARD_SKIP: If956dbdfcaf41641d8fcc4bd16381004bac8c342 Change-Id: Ie97c5c0910bf8cf58c675529bb69817a915720d5
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.