| commit | 3b67cdf291a977e91c6818e11b92948083bc8f7e | [log] [tgz] |
|---|---|---|
| author | Tao Bao <tbao@google.com> | Tue Feb 13 17:36:22 2018 +0000 |
| committer | android-build-merger <android-build-merger@google.com> | Tue Feb 13 17:36:22 2018 +0000 |
| tree | 868a54cc2cffe0f098aba2b92aa32868f1f610db | |
| parent | 53e5a438a83274945af98e15a9a5cf42b2e405ba [diff] | |
| parent | 000274fda1a4c1e6616e2bbab49981a78a0b3306 [diff] |
Merge changes Ia7ecd0e1,I33982473 am: 4a066a2cd2 am: b25e43bfcb am: 000274fda1 Change-Id: I360a5b5eeda4a3cfd9bd1145f36d030118eb8361
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.