| commit | af1b8acf4507b03d15e8f1ff446fae90fd6fc93b | [log] [tgz] |
|---|---|---|
| author | SzuWei Lin <szuweilin@google.com> | Sat Mar 24 12:15:09 2018 +0800 |
| committer | SzuWei Lin <szuweilin@google.com> | Sat Mar 24 12:15:09 2018 +0800 |
| tree | 292f38e99e82da181253a0e26f7c61b4d6fd3362 | |
| parent | c8e8aa00300905b66a24ae99bd4f72b682afbded [diff] | |
| parent | ac70cd2b8ca313f024acfcfd001816cc43f5ab5b [diff] |
resolve merge conflicts of ac70cd2b8ca313f024acfcfd001816cc43f5ab5b to pi-dev-plus-aosp Test: I solemnly swear I tested this conflict resolution. Change-Id: I2f5d33434dc20d252dd11e69416077f688355f3b
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.