Initial implementation of Chrome Early Loading Framework

chrome/app/chrome_exe_main_win.cc

Index: chrome/app/chrome_exe_main_win.cc
diff --git a/chrome/app/chrome_exe_main_win.cc b/chrome/app/chrome_exe_main_win.cc
index ecbb599923aed74e5aaef337cac2311f7a145b73..79844c568d66959f06e709c9122119d0f3da1d24 100644
--- a/chrome/app/chrome_exe_main_win.cc
+++ b/chrome/app/chrome_exe_main_win.cc
@@ -18,6 +18,7 @@
 #include "chrome/browser/policy/policy_path_parser.h"
 #include "chrome/common/chrome_paths_internal.h"
 #include "chrome/common/chrome_switches.h"
+#include "chrome_elf/chrome_elf_main.h"
 #include "components/breakpad/app/breakpad_client.h"
 #include "components/breakpad/app/breakpad_win.h"
 #include "content/public/app/startup_helper_win.h"
@@ -105,6 +106,8 @@ int APIENTRY wWinMain(HINSTANCE instance, HINSTANCE prev, wchar_t*, int) {
   // The exit manager is in charge of calling the dtors of singletons.
   base::AtExitManager exit_manager;
 
+  InitChromeElf();
+
   if (AttemptFastNotify(*CommandLine::ForCurrentProcess()))
     return 0;
 

[cpu_(ooo_6.6-7.5), 2013/11/07 19:29:32]

can we do the init after the fast notify?

If we fast notify we unload so the work done is lost afaik.

[gab, 2013/11/07 20:19:40]

This call doesn't actually do any work; all it does is force the addition of an
entry in the IAT for chrome_elf.dll which forces the load time dependency. A
comment should probably be added here to state this.

[cpu_(ooo_6.6-7.5), 2013/11/07 22:10:37]

Ok,then so still can called after? I just want to avoid a year from now somebody
putting code in the empty function. You can also bind to an exported variable
afaik.