| commit | 47970225d26a04c7de0abc03f8969aa303d4e794 | [log] [tgz] |
|---|---|---|
| author | Paul Duffin <paulduffin@google.com> | Fri Nov 10 14:52:22 2017 +0000 |
| committer | Paul Duffin <paulduffin@google.com> | Fri Jan 19 08:16:34 2018 +0000 |
| tree | 9fe16963bab85554511ac45cd367746aeb8fd41e | |
| parent | 968d6c00e5f9a998a2b117be84dca3ee73dd7cf5 [diff] |
Use Proguard -systemjars instead of -libraryjars Proguard -systemjars will correctly use the system libraries version of a duplicate class rather than the program's version. If USE_R8=true then use -libraryjars as R8's proguard emulation layer does not support -systemjars and it is unnecessary because R8 does not fail like proguard does when it comes across duplicate classes. Bug: 30188076 Bug: 69156675 Test: make checkbuild Change-Id: I99f0cb7a816ce34e5fa209803b7c538fd931d8a7
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.