commit | 8671e202018dcb0bcd1069035de3461e2251b850 | [log] [tgz] |
---|---|---|
author | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Thu Jul 20 04:10:22 2023 +0000 |
committer | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Thu Jul 20 04:10:22 2023 +0000 |
tree | 48dbdfb197c2cf1b7371eba7988487a07d445692 | |
parent | 17fe9b13a59c9184547ef0db242805a67f0e6708 [diff] | |
parent | 1a2b6b63541e719b45058040c4e23cdd47f1dd2a [diff] |
[coastguard skipped] Merge sparse cherrypicks from sparse-10529556-L00000000962081650 into udc-release. COASTGUARD_SKIP: I1a5d6af1c5dd1881ab36e45590f4c7fa98f8449d Change-Id: I647601bbb44bc0ea614415f53043753d630a0ad6
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.