| commit | 719b51b40079a89df2d1f66cf8407e26d4338063 | [log] [tgz] |
|---|---|---|
| author | Nicolas Geoffray <ngeoffray@google.com> | Wed Apr 03 01:15:27 2019 -0700 |
| committer | android-build-merger <android-build-merger@google.com> | Wed Apr 03 01:15:27 2019 -0700 |
| tree | 31a24be509b635477337a9c497658c5c0c81d2da | |
| parent | d800adb9799e8cf9377daddec5a13b62d3790517 [diff] | |
| parent | 2c142f1178ece01cecff59c48fe674bd25d0a1f2 [diff] |
Merge "Re-order the ext/framework boot jars in bootclasspath." am: 31a7dee48b am: 2c142f1178 Change-Id: Ic16d4172f0fe53059898a12a43311f7070f85a8c
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.