diff options
| author | cjhopman <cjhopman@chromium.org> | 2015-05-05 16:47:15 -0700 |
|---|---|---|
| committer | Commit bot <commit-bot@chromium.org> | 2015-05-05 23:47:46 +0000 |
| commit | e852f8d50a4c65f0de6fcc3753abdc8ba3b22a9e (patch) | |
| tree | 354a76a7839aa96d0332bb053f7e386872459dc5 /extensions/components | |
| parent | 1fb981a4e80a7a65071097eeb3170a30f0caf39c (diff) | |
| download | chromium_src-e852f8d50a4c65f0de6fcc3753abdc8ba3b22a9e.zip chromium_src-e852f8d50a4c65f0de6fcc3753abdc8ba3b22a9e.tar.gz chromium_src-e852f8d50a4c65f0de6fcc3753abdc8ba3b22a9e.tar.bz2 | |
Refactor proguard scripts
Currently, we use proguard from two places: proguard.py and apk_obfuscate.py.
These are used to preprocess libraries and to process full apks, respectively.
This extracts construction/running/filtering output of the actual proguard
command to a simple builder class that is then used in both places. This makes
some parts of how proguard is run to be more consistent between the two.
proguard.py now supports running proguard in the way needed for apks. (GN will
be using proguard.py instead of apk_obfuscate.py)
BUG=359249,478319
Review URL: https://codereview.chromium.org/1103013002
Cr-Commit-Position: refs/heads/master@{#328439}
Diffstat (limited to 'extensions/components')
0 files changed, 0 insertions, 0 deletions