Initial implementation of Chrome Early Loading Framework

chrome_elf/chrome_elf.gyp

Index: chrome_elf/chrome_elf.gyp
diff --git a/chrome_elf/chrome_elf.gyp b/chrome_elf/chrome_elf.gyp
new file mode 100644
index 0000000000000000000000000000000000000000..d8e5c95dae04d54d4a38ab955839c0f88a16d0bf
--- /dev/null
+++ b/chrome_elf/chrome_elf.gyp
@@ -0,0 +1,74 @@
+# Copyright 2013 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.
+{
+  'variables': {
+    'chromium_code': 1,
+  },
+  'includes': [
+    '../build/win_precompile.gypi',
+    '../chrome/version.gypi',
+  ],
+  'targets': [
+    {
+      'target_name': 'chrome_elf',
+      'type': 'shared_library',
+      'include_dirs': [
+        '..',
+      ],
+      'sources': [
+        'chrome_elf.def',
+        'chrome_elf_main.cc',
+        'chrome_elf_main.h',
+      ],
+      'actions' :  [
+        { # Construct a manifest file declaring chrome.exe's dependency on

[grt (UTC plus 2), 2013/11/07 03:04:23]

chrome_elf doesn't need these, does it? if i understand correctly, these
manifests are needed by whatever it is that links to chrome_elf. perhaps
chrome_elf/ could contain .gypi snippets meant to be included by targets that
link to it? take a look at build\grit_action.gypi and how it's used for an idea
of what i mean. apologies for not bringing this up earlier.

+          # chrome_elf.dll. This will be merged into chrome.exe.manifest and
+          # embedded into chrome.exe when it is built.
+          'action_name': 'chrome_exe_manifest',
+          'variables': {
+            'template_input_path':
+                '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)',
+          ],
+          'message': 'Generating <@(_outputs)'
+        },
+        { # Construct a manifest file (with the same name as the version_dir) so
+          # that chrome.exe identifies the version_dir as an assembly. This will
+          # be copied over to the version_dir by the installer script.
+          'action_name': 'version_assembly_manifest',
+          'variables': {
+            'template_input_path':
+                'version_assembly_manifest.template',
+          },
+          'inputs': [
+            '<(template_input_path)',
+            '<(version_path)',
+          ],
+          'outputs': [
+            '<(PRODUCT_DIR)/<(version_full).manifest',
+          ],
+          'action': [
+            'python', '<(version_py_path)',
+            '-f', '<(version_path)',
+            '<(template_input_path)',
+            '<@(_outputs)',
+          ],
+          'message': 'Generating <@(_outputs)'
+        },
+      ],
+    },
+  ],
+}