| commit | d1bea0e0255d2488d36a3181564233e7cd67eb41 | [log] [tgz] |
|---|---|---|
| author | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Fri Apr 21 08:00:01 2023 +0000 |
| committer | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Fri Apr 21 08:00:01 2023 +0000 |
| tree | 6e6cb4c557eec72302273a67b515331d5a36738a | |
| parent | 79ace9a004bcbb2a32623ddc85c47ce00686f402 [diff] | |
| parent | 28c55344e3e0d9768663fb6bfdb63599f8c3b623 [diff] |
[coastguard skipped] Merge sparse cherrypicks from sparse-9985660-L32500000960105907 into udc-d1-release. COASTGUARD_SKIP: Ic5bc137d18bc1416d5c732eb3124d1c18f0b86b7 Change-Id: I0f54fbc1f24b5042238fb29cd7673c6eb12c89d4
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.