Chromium Code Reviews| OLD | NEW |
|---|---|
| (Empty) | |
| 1 # Copyright 2014 The Chromium Authors. All rights reserved. | |
| 2 # Use of this source code is governed by a BSD-style license that can be | |
| 3 # found in the LICENSE file. | |
| 4 | |
| 5 # Generates an output manifest based on a Jinja2 templated manifest. | |
|
Peter Lundblad
2014/05/23 16:04:27
nit: s/an output/a/
Peter Lundblad
2014/05/23 16:04:27
nit: mention that this is expected to be included
David Tseng
2014/05/23 19:16:37
Done.
David Tseng
2014/05/23 19:16:37
I don't claim to be a grammar wiz, but greping for
| |
| 6 # The following variables must be set before including this file: | |
| 7 # | |
| 8 # template_manifest: a valid JSON file path. | |
|
Peter Lundblad
2014/05/23 16:04:27
nit: it's a path to a jinja2 file.
Peter Lundblad
2014/05/23 16:04:27
Usually file name variable end in -Ifle and _path
David Tseng
2014/05/23 19:16:37
Done.
| |
| 9 # output_manifest: file path with the resulting manifest. | |
|
Peter Lundblad
2014/05/23 16:04:27
s/with/for?
David Tseng
2014/05/23 19:16:37
Sure; why not.
| |
| 10 | |
| 11 { | |
| 12 'actions': [ | |
| 13 { | |
| 14 'action_name': 'generate_manifest', | |
| 15 'message': 'Generate manifest for <(_target_name)', | |
| 16 'variables': { | |
| 17 'is_guest_manifest%': 0, | |
| 18 }, | |
| 19 'inputs': [ | |
| 20 'tools/generate_manifest.py', | |
| 21 '<(template_manifest)', | |
| 22 ], | |
| 23 'outputs': [ | |
| 24 '<(output_manifest)' | |
| 25 ], | |
| 26 'action': [ | |
| 27 'python', | |
| 28 'tools/generate_manifest.py', | |
| 29 '-o', '<(output_manifest)', | |
| 30 '-g', '<(is_guest_manifest)', | |
| 31 '<(template_manifest)' | |
| 32 ], | |
| 33 }, | |
| 34 ], | |
| 35 } | |
| OLD | NEW |