| commit | f6224459ed0ef2860d79cd5e82f0e73d2223dd95 | [log] [tgz] |
|---|---|---|
| author | Søren Gjesse <sgjesse@google.com> | Fri Dec 01 06:54:30 2017 +0000 |
| committer | android-build-merger <android-build-merger@google.com> | Fri Dec 01 06:54:30 2017 +0000 |
| tree | d539b788d0706312a01ad23785907e4ad2e0108d | |
| parent | d3809175045d3e42b329d32e7a6bf1617b4ce5aa [diff] | |
| parent | c35d6f16c4bbc10cd1b4c12abadf2e582e3f0d7f [diff] |
Merge "Prepare for switching from Proguard to R8" am: 6af8e92040 am: efbd35a247 am: c35d6f16c4 Change-Id: I4786546f0dd44f7206488b0b1ddaa13400025392
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.