Chromium Code Reviews| Index: build/grit_action.gypi |
| =================================================================== |
| --- build/grit_action.gypi (revision 0) |
| +++ build/grit_action.gypi (revision 0) |
| @@ -0,0 +1,40 @@ |
| +# 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. |
| + |
| +# This file is meant to be included into an action to invoke grit in a |
| +# consistent manner. To use this the following variables need to be |
| +# defined: |
| +# grit_grd_file: string: grd file path |
| +# grit_out_dir: string: the output directory path |
| + |
| +# It would be really nice to do this with a rule instead of actions, but |
| +# the need to come up with inputs/outputs (via grit_info) on a per file |
| +# basis which can't currently be done. GYP rules could be extended to do |
|
Mark Mentovai
2011/03/25 20:16:53
I think you meant
“but it would need to determine
|
| +# this, but then every generator would need to be updated to handle this, |
| +# because that is when the rules are expanded/applied. |
| + |
| +{ |
| + 'variables': { |
| + 'grit_info_cmd': ['python', '<(DEPTH)/tools/grit/grit_info.py', |
| + '<@(grit_defines)'], |
| + 'grit_cmd': ['python', '<(DEPTH)/tools/grit/grit.py'], |
| + }, |
| + 'inputs': [ |
| + '<!@(<(grit_info_cmd) --inputs <(grit_grd_file))', |
| + ], |
| + 'outputs': [ |
| + '<!@(<(grit_info_cmd) --outputs \'<(grit_out_dir)\' <(grit_grd_file))', |
| + ], |
| + 'action': ['<@(grit_cmd)', |
| + '-i', '<(grit_grd_file)', 'build', |
| + '-o', '<(grit_out_dir)', |
| + '<@(grit_defines)' ], |
| + 'message': 'Generating resources from <(grit_grd_file)', |
| +} |
| + |
| +# Local Variables: |
| +# tab-width:2 |
| +# indent-tabs-mode:nil |
| +# End: |
| +# vim: set expandtab tabstop=2 shiftwidth=2: |
| Property changes on: build/grit_action.gypi |
| ___________________________________________________________________ |
| Added: svn:eol-style |
| + LF |