Enable the packed_resources target on Windows.

chrome/chrome.gyp

 # Copyright (c) 2011 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': {
     'chromium_code': 1,
 
     'variables': {
       'version_py_path': 'tools/build/version.py',
       'version_path': 'VERSION',
@@ skipping 1593 matching lines @@
             },
           },
           'configurations': {
             'Common_Base': {
               'msvs_target_platform': 'x64',
             },
           },
         },
       ]},  # 'targets'
     ],  # OS=="win"
-    ['os_posix == 1 and OS != "mac"', {
+    ['OS != "mac"', {
       'targets': [{
         'target_name': 'packed_resources',
         'type': 'none',
         'variables': {
           'repack_path': '../tools/data_pack/repack.py',
         },
         'actions': [
           # TODO(mark): These actions are duplicated for the Mac in the
           # chrome_dll target.  Can they be unified?
           #
@@ skipping 44 matching lines @@
               'conditions': [
                 ['branding=="Chrome"', {
                   'branding_flag': ['-b', 'google_chrome',],
                 }, {  # else: branding!="Chrome"
                   'branding_flag': ['-b', 'chromium',],
                 }],
               ],
             },
             'inputs': [
               'tools/build/repack_locales.py',
-              # NOTE: Ideally the common command args would be shared amongst
-              # inputs/outputs/action, but the args include shell variables
-              # which need to be passed intact, and command expansion wants
-              # to expand the shell variables. Adding the explicit quoting
-              # here was the only way it seemed to work.
-              '>!@(<(repack_locales_cmd) -i <(branding_flag) -g \'<(grit_out_dir)\' -s \'<(SHARED_INTERMEDIATE_DIR)\' -x \'<(INTERMEDIATE_DIR)\' <(locales))',
+              '<!@pymod_do_main(repack_locales -i <(branding_flag) -g <(grit_out_dir) -s <(SHARED_INTERMEDIATE_DIR) -x <(INTERMEDIATE_DIR) <(locales))'
             ],
             'outputs': [
-              '>!@(<(repack_locales_cmd) -o -g \'<(grit_out_dir)\' -s \'<(SHARED_INTERMEDIATE_DIR)\' -x \'<(INTERMEDIATE_DIR)\' <(locales))',
+              '<!@pymod_do_main(repack_locales -o -g <(grit_out_dir) -s <(SHARED_INTERMEDIATE_DIR) -x <(INTERMEDIATE_DIR) <(locales))'

[Nico, 2011/08/12 21:46:25]

I'm always unsure about the difference between < and > (one is "early variable",
one is "late variable", but I don't know why this is important) – why was this
necessary?

[tony, 2011/08/12 21:53:36]

I don't understand the difference either.  I was just copying from
build/grit_action.gypi.

             ],
             'action': [
               '<@(repack_locales_cmd)',
               '<@(branding_flag)',
               '-g', '<(grit_out_dir)',
               '-s', '<(SHARED_INTERMEDIATE_DIR)',
               '-x', '<(INTERMEDIATE_DIR)',
               '<@(locales)',
             ],
           },
         ],
         # We'll install the resource files to the product directory.
         'copies': [
           {
             'destination': '<(PRODUCT_DIR)/locales',
             'files': [
-              '>!@(<(repack_locales_cmd) -o -g \'<(grit_out_dir)\' -s \'<(SHARED_INTERMEDIATE_DIR)\' -x \'<(INTERMEDIATE_DIR)\' <(locales))',
+              '<!@pymod_do_main(repack_locales -o -g <(grit_out_dir) -s <(SHARED_INTERMEDIATE_DIR) -x <(INTERMEDIATE_DIR) <(locales))'
             ],
           },
           {
             'destination': '<(PRODUCT_DIR)',
             'files': [
               '<(INTERMEDIATE_DIR)/repack/chrome.pak'
             ],
           },
         ],
       }],  # targets
-    }],  # os_posix == 1 and OS != "mac"
+    }],  # OS != "mac"
   ],  # 'conditions'
 }