commit | 1d64623105b4f7bae84b699034994d576d6d93dc | [log] [tgz] |
---|---|---|
author | Dan Willemsen <dwillemsen@google.com> | Fri Nov 17 13:11:26 2017 -0800 |
committer | Colin Cross <ccross@android.com> | Thu Dec 28 17:22:19 2017 +0000 |
tree | 2fb26d6c22f52414c1231120c0c5eacf0b286417 | |
parent | 5b82359f8575ea87dd780cca48128dfa2aceafa8 [diff] |
Export proguard flags from static android libraries and aar prebuilts Test: m Contacts, classes-proguard.jar has same contents Test: rm -rf out; tapas Contacts; m Change-Id: Id7a92fb2c44913bccbfcbeae127355b4de588e4d Merged-In: Id7a92fb2c44913bccbfcbeae127355b4de588e4d (cherry picked from commit 1417c177ac9b942c4f1ae602f420444c72a90d6a)
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.