Provide script/gypi support for manifest generation

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

 # Copyright 2014 The Chromium Authors. All rights reserved.
 # Use of this source code is governed by a BSD-style license that can be
 # found in the LICENSE file.
 
 {
   'variables': {
     'chromevox_dest_dir': '<(PRODUCT_DIR)/resources/chromeos/chromevox',
   },
   'targets': [
     {
       'target_name': 'chromevox_resources',
       'type': 'none',
       'dependencies': [
         'chromevox_assets',
+        'chromevox_guest_manifest',
         'chromevox_static_files',
         'chromevox_strings',
         'chromevox_uncompiled_js_files',
         '<(DEPTH)/chrome/third_party/chromevox/chromevox.gyp:chromevox_third_party_resources',
       ],
       'conditions': [
         ['disable_nacl==0 and disable_nacl_untrusted==0', {
           'dependencies': [
             '<(DEPTH)/third_party/liblouis/liblouis_nacl.gyp:liblouis_nacl_wrapper_nacl',
           ],
@@ skipping 149 matching lines @@
             # TODO(plundblad): Change to use PRODUCT_DIR when we have
             # translations.
             'grit_out_dir': '<(SHARED_INTERMEDIATE_DIR)/resources/chromeos/chromevox',
             # We don't generate any RC files, so no resource_ds file is needed.
             'grit_resource_ids': '',
           },
           'includes': [ '../../../../../build/grit_action.gypi' ],
         },
       ],
     },
+    {
+      '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', ],
+    },
   ],
 }