Index: chrome/chrome_elf.gypi |
diff --git a/chrome/chrome_elf.gypi b/chrome/chrome_elf.gypi |
new file mode 100644 |
index 0000000000000000000000000000000000000000..100596558fa894217f39360ac386c8841bcbd79e |
--- /dev/null |
+++ b/chrome/chrome_elf.gypi |
@@ -0,0 +1,55 @@ |
+{ |
+ |
+ 'includes': [ |
+ 'version.gypi', |
+ ], |
+ 'targets': [ |
+ { |
+ 'target_name': 'chrome_elf', |
grt (UTC plus 2)
2013/11/05 03:08:36
does this target depend on anything in src/chrome?
Cait (Slow)
2013/11/05 05:39:06
I was wondering this too. I've moved it up a level
|
+ 'type': 'shared_library', |
+ 'include_dirs': [ |
+ '..', |
+ ], |
+ 'sources': [ |
+ 'chrome_elf/chrome_elf.def', |
+ 'chrome_elf/chrome_elf_main.cc', |
+ 'chrome_elf/chrome_elf_main.h', |
+ ], |
+ 'dependencies' : [ |
+ 'chrome_exe_manifest', |
+ ] |
+ }, |
+ { |
+ 'target_name': 'chrome_exe_manifest', |
+ 'type': 'none', |
+ 'sources': [ |
+ 'chrome_elf/chrome_exe_manifest.template', |
+ ], |
+ 'rules': [ |
robertshield
2013/11/05 02:23:55
Thinking about this a bit more, I believe there is
Cait (Slow)
2013/11/05 05:39:06
Done.
|
+ { |
+ 'rule_name': 'chrome_exe_manifest', |
+ 'extension': 'template', |
+ 'variables': { |
+ 'template_input_path': |
+ 'chrome_elf/chrome_exe_manifest.template', |
+ }, |
+ 'inputs': [ |
+ '<(template_input_path)', |
+ '<(version_path)', |
+ ], |
+ 'outputs': [ |
+ '<(SHARED_INTERMEDIATE_DIR)/chrome_elf/version_assembly.manifest', |
+ ], |
+ 'action': [ |
+ 'python', '<(version_py_path)', |
+ '-f', '<(version_path)', |
+ '<(template_input_path)', |
+ '<@(_outputs)', |
+ ], |
+ 'process_outputs_as_sources': 0, |
+ 'message': 'Generating additional manifest files' |
+ }, |
+ ], |
+ }, |
+ ], |
+} |