| commit | 0cb5dfb3dd43e2cefaa969a52568f55720570009 | [log] [tgz] |
|---|---|---|
| author | Daniel Norman <danielnorman@google.com> | Mon Jul 29 17:50:44 2019 -0700 |
| committer | android-build-merger <android-build-merger@google.com> | Mon Jul 29 17:50:44 2019 -0700 |
| tree | 5ad7bae59cd588e56307ea1e8ab804f545e3cdeb | |
| parent | 4b8a9d94756da7b055f288861554528e24921790 [diff] | |
| parent | 3f9554b59ae3703d3e656303d8564027f42e27c2 [diff] |
Merge "Adds new merge builds script for use in merging two non-dist builds." am: a85f0ee8a2 am: 3f9554b59a Change-Id: I4a693e2122b1ddefd1b4166d6218055d5636e49d
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.