| commit | a3e54cd24d985b48b8cbab554b6bc7da97b32a4e | [log] [tgz] |
|---|---|---|
| author | Colin Cross <ccross@android.com> | Thu May 10 22:36:19 2018 -0700 |
| committer | android-build-merger <android-build-merger@google.com> | Thu May 10 22:36:19 2018 -0700 |
| tree | 0e530743ccdee327e0ac2aa45c2ba5dd0e86d116 | |
| parent | 4f2b09be684eaa523a3596c44a57cefc4f499d4e [diff] | |
| parent | d3a1fa618f796f7f43556c422aaca62454ccdd3c [diff] |
Merge changes Ie3d4536b,If2504b7d,I411844fb am: fc56b59db4 am: d3a1fa618f Change-Id: Id5b5b7d398f4ee2c2acbca24f169728ae940cc61
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.