| commit | c85667a77ea4d343ddf2999632aad2fdcbcd7686 | [log] [tgz] |
|---|---|---|
| author | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Tue Aug 01 01:33:30 2023 +0000 |
| committer | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Tue Aug 01 01:33:30 2023 +0000 |
| tree | e1569dc5dac70ccd170a64f0088c3479bf6b227b | |
| parent | dc3a78c5e31bfc3adc94b7de44ee8e798cfd6249 [diff] | |
| parent | 8a9ae8cb7b5acb4adce809a09a400da9ff775687 [diff] |
[coastguard skipped] Merge sparse cherrypicks from sparse-10589763-L91700000962314517 into udc-release. COASTGUARD_SKIP: I08282b324b41e4bc34b9b4976a27bdd2eff49168 Change-Id: I5d7c61e1e6d4f01481a68b75b77425fc86a47447
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.