| commit | 56ce968ae03b96f274e9d614b6553a53d7014c11 | [log] [tgz] |
|---|---|---|
| author | Colin Cross <ccross@android.com> | Tue Apr 16 17:11:06 2019 -0700 |
| committer | android-build-merger <android-build-merger@google.com> | Tue Apr 16 17:11:06 2019 -0700 |
| tree | 9725e99356dae752d02521dc859d5c71bac776ab | |
| parent | c66d72100ea087ccbbf7b2ecf1c36cb0ff647baa [diff] | |
| parent | 15e4096803c37557df9b722d463f8c1afb94e966 [diff] |
[automerger skipped] Merge "Add default proguard flags from guava" am: 727ef10366 am: 15e4096803 -s ours am skip reason: change_id Ia9948d597538a16c5b7ab26a2e41eebde52e7427 with SHA1 b4917146aa is in history Change-Id: I0c2dd9f1cd8e47b9411dc2e92e3d9c6f112ab083
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.