| commit | 989d012b59e493d02bbe6f56b8093d4cd47f86d3 | [log] [tgz] |
|---|---|---|
| author | Tao Bao <tbao@google.com> | Wed Jul 03 16:32:24 2019 -0700 |
| committer | android-build-merger <android-build-merger@google.com> | Wed Jul 03 16:32:24 2019 -0700 |
| tree | 6a078f6f64eb3106d6e2beb8eaad3b28a02554c3 | |
| parent | 6c83d75d8794a94940e1bd3956a3284c4578730f [diff] | |
| parent | 06429d7048a4a5ea76948ffd06c78f16bd09296b [diff] |
[automerger skipped] Change the condition for building super_empty.img. am: 06429d7048 -s ours am skip reason: change_id I277f087eab45663a6c3b33333d16e9e576c1c25c with SHA1 48a2feb670 is in history Change-Id: Ib9afcae59717d1b25d9119b50e8e7e76c12726a8
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.