| commit | df1cc96e6a617121e222bd6ee75b28f2a515074e | [log] [tgz] |
|---|---|---|
| author | Dan Shi <dshi@google.com> | Mon Jul 15 11:25:45 2019 -0700 |
| committer | android-build-merger <android-build-merger@google.com> | Mon Jul 15 11:25:45 2019 -0700 |
| tree | cad342507a4fb4654caaddedb709f8edb440e0f7 | |
| parent | 29bbd5d074a369b0407864a0e67f6ddb046df96e [diff] | |
| parent | bf896d7eea94a944c6c1dd27442a04fbfd785c19 [diff] |
Merge "[automerger skipped] Update auto-gen test config template with EXTRA_CONFIGS placeholder am: 8d5459fc6d -s ours am: 757a503749 -s ours am: bf896d7eea -s ours am skip reason: change_id I2fdae79d45fd1e5866ee94d1f0e59df106be2a87 with SHA1 4c55da09db is in history Change-Id: Iba55a0b3c1a985ee0b1759c67a1ebd033d8d7d85
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.