commit | cd929c7a90668bdac60f3d533cdd1852ee8e2d23 | [log] [tgz] |
---|---|---|
author | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Wed Dec 18 03:33:21 2019 +0000 |
committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Wed Dec 18 03:33:21 2019 +0000 |
tree | 3832afd5510dcc16dfbb9f50573018ca8ee20f77 | |
parent | 52371a2308d9e49a5acf85491734d0bd3b7ed768 [diff] | |
parent | 7de4cd5dc53ed25fab2ef0cad8ede2035087ca57 [diff] |
[automerger skipped] Merge "Remove Soong intermdiates after moving image mutator" am: ff81b9d1d0 am: a69bb55b5b am: 7de4cd5dc5 -s ours am skip reason: Change-Id I76f19a4504b8231755009ab200447613f02b85cf with SHA-1 559ab613ae is in history Change-Id: I2e9a4a3a80691ce9616d7f85b5558edf15548d85
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.