[blink-in-js] Migrate resources required for blink-in-js to grd - part 3

Source/core/core_generated.gyp

 #
 # Copyright (C) 2013 Google Inc. All rights reserved.
 #
 # Redistribution and use in source and binary forms, with or without
 # modification, are permitted provided that the following conditions are
 # met:
 #
 #     * Redistributions of source code must retain the above copyright
 # notice, this list of conditions and the following disclaimer.
 #     * Redistributions in binary form must reproduce the above
@@ skipping 165 matching lines @@
           'inputs': [
              '../build/scripts/make_private_script_source.py',
              '<@(_private_script_files)',
            ],
            'outputs': [
              '<(blink_core_output_dir)/PrivateScriptSourcesForTesting.h',
            ],
            'action': [
              'python',
              '../build/scripts/make_private_script_source.py',
+             '--for-testing',

[haraken, 2014/09/10 07:30:32]

--verbose ?

[vivekg, 2014/09/10 07:46:56]

The test resources are not packaged in the grd generated pak files. For the
tests, these will be still embedded in the binary. I am working on how to
migrate the test resources also out of the binary but that shouldn't stop us
from landing these changes.

To differentiate that, I used '--for-testing'. I think '--verbose' wouldn't
serve the purpose due to different literal meaning. WDYT? 

              '<@(_outputs)',
              '<@(_private_script_files)'
            ],
         },
         {
           'action_name': 'HTMLEntityTable',
           'inputs': [
             'html/parser/create-html-entity-table',
             'html/parser/HTMLEntityNames.in',
           ],
@@ skipping 611 matching lines @@
             '../build/scripts/rule_bison.py',
             '<(RULE_INPUT_PATH)',
             '<(blink_core_output_dir)',
             '<(bison_exe)',
           ],
         },
       ],
     },
   ],
 }