0

Remove references to or invocations of vulcanize.py. It's deleted.

Vulcanize now happens dynamically with GN/Ninja. \o/

R=dpapad@chromium.org
BUG=673825
NOTRY=true

Review-Url: https://codereview.chromium.org/2690743003
Cr-Commit-Position: refs/heads/master@{#449875}
This commit is contained in:
dbeam
2017-02-11 12:58:07 -08:00
committed by Commit bot
parent 772ff4cd3d
commit d51c79fa34
2 changed files with 0 additions and 16 deletions
docs
third_party/polymer/v1_0

@ -10,19 +10,6 @@ use_vulcanize = true
is_debug = false
```
If you make local changes, you likely need to re-run:
```
$ chrome/browser/resources/vulcanize.py
```
And rebuild Chrome to see effects. vulcanize.py will result in local changes to
*crisper* and *vulcanized* files that you must currently check in.
*NOTE: Vuclanize is being integrated directly into
[GN/Ninja](https://crbug.com/673825), so this workflow is likely to change
soon.*
## How is the code optimized?
### Resource combination

@ -108,9 +108,6 @@ python create_components_summary.py > components_summary.txt
echo 'Creating GYP files for interfaces and externs...'
./generate_gyp.sh
echo 'Vulcanizing dependent UIs...'
python ../../../chrome/browser/resources/vulcanize.py
popd > /dev/null
echo 'Searching for unused elements...'