| commit | 41fee1dcf48687847e54eb873935c50e8804c8a6 | [log] [tgz] |
|---|---|---|
| author | android-build-team Robot <android-build-team-robot@google.com> | Thu Aug 15 04:36:26 2019 +0000 |
| committer | android-build-team Robot <android-build-team-robot@google.com> | Thu Aug 15 04:36:26 2019 +0000 |
| tree | 4c8e69efd2e9f706a87fe12aa5c964ab3d8276da | |
| parent | 687e845c10b23c9d83074e0956aed03f8184b1f9 [diff] | |
| parent | df238b4e41d29aa02988d6d8da8ed8e531a7a79f [diff] |
Snap for 5803298 from df238b4e41d29aa02988d6d8da8ed8e531a7a79f to qt-aml-release Change-Id: I883c94b2251bf7e1deb349df5adf4d9954b0df14
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.