| commit | 53c86dec7315645ce6ec4bcc56fe00d06b41a567 | [log] [tgz] |
|---|---|---|
| author | Tao Bao <tbao@google.com> | Thu Oct 11 14:18:53 2018 -0700 |
| committer | android-build-merger <android-build-merger@google.com> | Thu Oct 11 14:18:53 2018 -0700 |
| tree | 063a69b051793c9015faa1fe434107d9aba4a9f5 | |
| parent | 8a4b28c5ad2ae5682c00341bae6eb864e3709237 [diff] | |
| parent | 6c22649500cd360488bed88f29dfd68e9a634588 [diff] |
Merge "releasetools: Move build_image.RunCommand into common.py." am: b2dd1b6365 am: 6c22649500 Change-Id: I6257243b7bee2ea8fdc45cd3f1841417307e0f73
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.