| commit | 1a3bf4f5e5576c20204e804936d43d9ed7b1c48b | [log] [tgz] |
|---|---|---|
| author | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Wed Aug 30 23:18:08 2023 +0000 |
| committer | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Wed Aug 30 23:18:08 2023 +0000 |
| tree | 41327747eead556153862e520e34a96fd79e6502 | |
| parent | 2c3d5b1e1c6316a2c1cdd95906a028abc83f97f3 [diff] | |
| parent | f219ff7649462df6b7f9eb117f8aa9b7e21909ab [diff] |
[coastguard skipped] Merge sparse cherrypicks from sparse-10740638-L17800000962853027 into udc-release. COASTGUARD_SKIP: I456c1b17576d0a0253eb5fd165f5b6cae953e63b Change-Id: I33992aa5a69a4d3a913d39a5eadeaf8586fe11c4
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.