| commit | 702b76766ed45845365b0aada46d7edbacb575d3 | [log] [tgz] |
|---|---|---|
| author | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Mon Aug 14 21:31:07 2023 +0000 |
| committer | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Mon Aug 14 21:31:07 2023 +0000 |
| tree | 5e21b6ca1eff32294053457f0133f1b625293b6d | |
| parent | a63765215416a83b0ad23d2f1b2cc40353092f0d [diff] | |
| parent | 38d9f285a8a2708b1d6a22168a794f9c5dbc5f8e [diff] |
[coastguard skipped] Merge sparse cherrypicks from sparse-10656238-L18400000962566963 into udc-release. COASTGUARD_SKIP: I2b085437c4a1bd90a8dcede4c44d1beadf3b7802 Change-Id: Ib90eee1b8ae3ca8fb48ad4f18f5205c03b27dc06
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.