commit | e194bcad19034b03a4215939b89e8b809d6d9597 | [log] [tgz] |
---|---|---|
author | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Sun Aug 20 08:35:55 2023 +0000 |
committer | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Sun Aug 20 08:35:55 2023 +0000 |
tree | 11c2286587ac5eaf83322348226273d022f137dd | |
parent | cf041d064ae7d1fb88aaef8aeda2aff78863ee55 [diff] | |
parent | 544be10b2a32218568f1f312d4567c981e7e3e47 [diff] |
[coastguard skipped] Merge sparse cherrypicks from sparse-10685236-L22000000962658982 into udc-release. COASTGUARD_SKIP: Ib437ebfe276de1995b48a7a7756ed43f857f85e8 Change-Id: I114fb0c1e435e361114d80dac6ff018779ecf97f
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.