| commit | 947713150de87be03725387512fe4b57fed6f7cc | [log] [tgz] |
|---|---|---|
| author | android-build-team Robot <android-build-team-robot@google.com> | Tue Oct 20 00:02:12 2020 +0000 |
| committer | android-build-team Robot <android-build-team-robot@google.com> | Tue Oct 20 00:02:12 2020 +0000 |
| tree | aff0bbd7fb9145dc5c7487ee68bfd7f5136b0a02 | |
| parent | 5ecc3a5c13a27e54646a6bae90af7465ddf82cee [diff] | |
| parent | ee1f30a6f35669728df6396c3395a2acdd668187 [diff] |
Snap for 6916203 from ee1f30a6f35669728df6396c3395a2acdd668187 to mainline-release Change-Id: I474ef1b1b9146f25bae1df428b520a555eaed5ed
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.