| commit | d207aebdd5ea933f6d471bda9021420906e2c6b7 | [log] [tgz] |
|---|---|---|
| author | Mathieu Chartier <mathieuc@google.com> | Mon Aug 26 14:24:19 2019 -0700 |
| committer | android-build-merger <android-build-merger@google.com> | Mon Aug 26 14:24:19 2019 -0700 |
| tree | 5271b2a4156075a5a5e3f96e917fc12c10a55f3a | |
| parent | 651c7af5c0158865f7229d2829d34a1f8e09c821 [diff] | |
| parent | 6cf820939c0843453efcdad7dff37ddfeb0e3d14 [diff] |
[automerger skipped] Merge "Revamp nopreload configuration" am: bca3111cfa am: 066f23b78a am: a200fb7d45 am: d76b692563 am: 6cf820939c -s ours am skip reason: change_id I97a3a25c3094f84e130e02692b02832795ee6ef1 with SHA1 6f8fda4937 is in history Change-Id: I30269aea93bf59be3233ee6049860c6bd6490f48
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.