media/webrtc/trunk/build/grit_action.gypi

Wed, 31 Dec 2014 06:09:35 +0100

author
Michael Schloh von Bennewitz <michael@schloh.com>
date
Wed, 31 Dec 2014 06:09:35 +0100
changeset 0
6474c204b198
permissions
-rw-r--r--

Cloned upstream origin tor-browser at tor-browser-31.3.0esr-4.5-1-build1
revision ID fc1c9ff7c1b2defdbc039f12214767608f46423f for hacking purpose.

michael@0 1 # Copyright (c) 2011 The Chromium Authors. All rights reserved.
michael@0 2 # Use of this source code is governed by a BSD-style license that can be
michael@0 3 # found in the LICENSE file.
michael@0 4
michael@0 5 # This file is meant to be included into an action to invoke grit in a
michael@0 6 # consistent manner. To use this the following variables need to be
michael@0 7 # defined:
michael@0 8 # grit_grd_file: string: grd file path
michael@0 9 # grit_out_dir: string: the output directory path
michael@0 10
michael@0 11 # It would be really nice to do this with a rule instead of actions, but it
michael@0 12 # would need to determine inputs and outputs via grit_info on a per-file
michael@0 13 # basis. GYP rules don’t currently support that. They could be extended to
michael@0 14 # do this, but then every generator would need to be updated to handle this.
michael@0 15
michael@0 16 {
michael@0 17 'variables': {
michael@0 18 'grit_cmd': ['python', '<(DEPTH)/tools/grit/grit.py'],
michael@0 19 },
michael@0 20 'inputs': [
michael@0 21 '<!@pymod_do_main(grit_info <@(grit_defines) --inputs <(grit_grd_file))',
michael@0 22 ],
michael@0 23 'outputs': [
michael@0 24 '<!@pymod_do_main(grit_info <@(grit_defines) --outputs \'<(grit_out_dir)\' <(grit_grd_file))',
michael@0 25 ],
michael@0 26 'action': ['<@(grit_cmd)',
michael@0 27 '-i', '<(grit_grd_file)', 'build',
michael@0 28 '-fGRIT_DIR/../gritsettings/resource_ids',
michael@0 29 '-o', '<(grit_out_dir)',
michael@0 30 '<@(grit_defines)' ],
michael@0 31 'msvs_cygwin_shell': 0,
michael@0 32 'message': 'Generating resources from <(grit_grd_file)',
michael@0 33 }

mercurial