| commit | e93694fb9014980b3cc27da20d83f4ed2e0958b1 | [log] [tgz] |
|---|---|---|
| author | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Thu Feb 13 16:46:10 2020 +0000 |
| committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Thu Feb 13 16:46:10 2020 +0000 |
| tree | 6ab52e101d5a5320c4463aecc661af2160962e97 | |
| parent | d08f3c93321d255ef9aa7bdf9490461615c59797 [diff] | |
| parent | 451879d2deee0ca6b1d452218b32434334720cce [diff] |
Merge "Modify D8 template to not have inputs under the output directory." am: 8e3f73576f am: 9c2afcf9c6 am: 451879d2de Change-Id: I85c6a195c345c7799cc6ed2df22dd30320b76a2e
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.