[Android] Fix proguard
commit6593b277eafa971ae5e05a5200e6757e71684628
authorcjhopman@chromium.org <cjhopman@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>
Sat, 18 May 2013 02:33:37 +0000 (18 02:33 +0000)
committercjhopman@chromium.org <cjhopman@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>
Sat, 18 May 2013 02:33:37 +0000 (18 02:33 +0000)
tree393077d1827d94333c9b14e3563a3bd54e44f664
parent977b69904d8625342ca73b3f1636ba716a565c7b
[Android] Fix proguard

Gyp supports only very limited ways of changing behavior based upon
CONFIGURATION_NAME. Particularly, it does not support the way that was
supposed to enable/disable use of proguard.

Instead of trying to switch behavior in gyp, instead pass
CONFIGURATION_NAME, proguard_enabled, and
proguard_enabled_dex_input_path to dex.py and switch the behavior
there.

This also extracts the dex actions into build/android/dex_action.gypi
and uses that for the actions in both build/java.gypi and
build/java_apk.gypi.

BUG=240837

Review URL: https://chromiumcodereview.appspot.com/15231006

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@200958 0039d316-1c4b-4281-b951-d872f2087c98
build/android/dex_action.gypi [new file with mode: 0644]
build/android/gyp/dex.py
build/java.gypi
build/java_apk.gypi