Provide script/gypi support for manifest generation

chrome/browser/resources/chromeos/chromevox/chromevox.gyp

Index: chrome/browser/resources/chromeos/chromevox/chromevox.gyp
diff --git a/chrome/browser/resources/chromeos/chromevox/chromevox.gyp b/chrome/browser/resources/chromeos/chromevox/chromevox.gyp
index 6bc51f83b67b3b962c6422e3156176289ebab06a..42cf7d0cea6810f6c8a36ba4828efd3f4c78a0b4 100644
--- a/chrome/browser/resources/chromeos/chromevox/chromevox.gyp
+++ b/chrome/browser/resources/chromeos/chromevox/chromevox.gyp
@@ -12,6 +12,7 @@
       'type': 'none',
       'dependencies': [
         'chromevox_assets',
+        'chromevox_guest_manifest',
         'chromevox_static_files',
         'chromevox_strings',
         'chromevox_uncompiled_js_files',
@@ -181,5 +182,15 @@
         },
       ],
     },
+    {
+      'target_name': 'chromevox_guest_manifest',
+      'type': 'none',
+      'variables': {
+        'base_manifest': 'manifest.json',
+        'override_manifest': 'manifest_guest_overrides.json',

[Peter Lundblad, 2014/05/22 00:28:25]

Shouldn't have build rules that generate files into the source tree.
Either we need to find a way to include these from the generated tree
as resources (we could actually load the manifests from the filesystem
instead of from .pak files as we do for everything else), or we
should make this a separate script and enforce it being run by PRESUBMIT.
I like the first better, but can live with the second since it is still
semi-automated.

[David Tseng, 2014/05/22 02:42:04]

The first suggestion would deviate from how other component extension load their
manifests, so I'm not sure that would work. What if we made this rule a
dependency of packed resources? Let's chat about this one in person.

+        'output_manifest': 'manifest_guest.json',
+      },
+      'includes': [ 'merge_manifests.gypi', ],
+    },
   ],
 }