commit | 2a4067259799fadd6d5a289347e50fe81caa5f97 | [log] [tgz] |
---|---|---|
author | Colin Cross <ccross@android.com> | Fri Dec 13 16:23:11 2019 -0800 |
committer | Colin Cross <ccross@android.com> | Fri Dec 13 16:23:11 2019 -0800 |
tree | 54f8f5da46bb8cff32e4f7c6a496626dc880e3c6 | |
parent | 066fac7c8ca3ea5e6381e4f88973461a6740eee0 [diff] |
Initialize common_proguard_flags for each module Id938aa35e87c9c69769a3184dfea06fd02299688 removed the initial assignment to common_proguard_flags, which both makes it grow as each module is parsed and also turns it into a lazily evaluated variable. That causes the flags passed to R8 to be the flags computed for the current module multiplied by the number of previously parsed modules. Fixes: 146150575 Test: m checkbuild Change-Id: I87c9625496f482896be6867124f2f12ff662cd57
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.