MD Downloads: add a use_vulcanize option to Chrome

chrome/chrome_features.gypi

Index: chrome/chrome_features.gypi
diff --git a/chrome/chrome_features.gypi b/chrome/chrome_features.gypi
index 06488b1e8afce75d860df7a074cc4dcb72734685..042e43abe98a164cf16ab45d47a4c6039fc78a17 100644
--- a/chrome/chrome_features.gypi
+++ b/chrome/chrome_features.gypi
@@ -21,17 +21,21 @@
           'enable_google_now%': 1,
         }]
       ],
+
+      'use_vulcanize%': 1,

[Nico, 2015/12/30 14:29:22]

shouldn't this default to 0?

[Dan Beam, 2015/12/30 17:11:12]

no

[Dan Beam, 2015/12/30 17:22:53]

i only asked you to review part of this CL, so you may not have a great idea of
the bigger picture here.  i've updated the CL description, which will hopefully
help, but just to make sure...

right chrome contains:
1) the old downloads page
2) a debug version of the new downloads page
3) a vulcanized version of the downloads page

eventually it should only contain:
1) a vulcanized version of the new (and only) downloads page

steps to get to here ^:
1) land this CL to make debug and vulcanized versions mutually exclusive
2) remove the old version when we're shipped

i assume both ^ these steps to remove code will help with size

     },
 
     # Anything in the conditions needs to be copied to the outer scope to be
     # accessible.
     'enable_google_now%': '<(enable_google_now)',
     'android_java_ui%': '<(android_java_ui)',
+    'use_vulcanize%': '<(use_vulcanize)',
 
     # Grit defines based on the feature flags. These must be manually added to
     # grit targets.
     'chrome_grit_defines': [
       '-D', 'enable_google_now=<(enable_google_now)',
+      '-D', 'use_vulcanize=<(use_vulcanize)',
     ]
   },
 }