OLD | NEW |
---|---|
(Empty) | |
1 # Copyright 2013 The Chromium Authors. All rights reserved. | |
gab
2013/11/11 20:11:38
This isn't really chrome_elf specific (beyond the
Cait (Slow)
2013/11/12 16:33:54
From discussing with grt, I have a follow up patch
gab
2013/11/12 18:24:10
What's that plan? It feels weird to dump everythin
| |
2 # Use of this source code is governed by a BSD-style license that can be | |
3 # found in the LICENSE file. | |
4 | |
5 # This file contains an action which can be used to construct a manifest file | |
6 # with the same name as the version directory so that chrome.exe identifies the | |
7 # version directory as an assembly. This will be copied over to the version | |
8 # directory by the installer script. | |
9 | |
10 # To use this the following variables need to be defined: | |
11 # version_path: string: path to file containing version data (e.g. | |
12 # chrome/VERSION). | |
13 # version_py_path: string: path to file containing version script (e.g. | |
14 # chrome/tools/build/version.py). | |
15 # version_full: string: version string in WWWW.X.YYYY.Z form. | |
gab
2013/11/11 20:11:38
Why WWWW.X.YYYY.Z? Nothing prevents X/Z to be more
Cait (Slow)
2013/11/12 16:33:54
Done.
| |
16 | |
17 | |
18 { | |
19 'variables': { | |
20 'template_input_path': | |
21 '<(DEPTH)/chrome_elf/version_assembly_manifest.template', | |
22 }, | |
23 'inputs': [ | |
24 '<(template_input_path)', | |
25 '<(version_path)', | |
26 ], | |
27 'outputs': [ | |
28 '<(PRODUCT_DIR)/<(version_full).manifest', | |
29 ], | |
30 'action': [ | |
31 'python', '<(version_py_path)', | |
32 '-f', '<(version_path)', | |
33 '<(template_input_path)', | |
34 '<@(_outputs)', | |
35 ], | |
36 'message': 'Generating <@(_outputs)', | |
37 } | |
OLD | NEW |