Home | History | Annotate | only in /external/chromium_org/chrome_elf
Up to higher level directory
NameDateSize
chrome_elf.def03-Jun-2014214
chrome_elf.gyp03-Jun-20141.4K
chrome_elf_main.cc03-Jun-2014537
chrome_elf_main.h03-Jun-2014318
chrome_elf_types.h03-Jun-2014380
chrome_exe_manifest.template03-Jun-2014360
chrome_exe_manifest_action.gypi03-Jun-20141.1K
DEPS03-Jun-201420
ntdll_cache.cc03-Jun-20141.9K
ntdll_cache.h03-Jun-2014458
ntdll_cache_unittest.cc03-Jun-2014915
OWNERS03-Jun-201465
README03-Jun-2014902
version_assembly_manifest.template03-Jun-2014253
version_assembly_manifest_action.gypi03-Jun-20141.2K

README

      1 Chrome Early Loading Framework (aka ChromeELF)
      2 
      3 chrome_elf.dll is shipped in Chrome's version directory to ease updates,
      4 and is loaded early in chrome.exe's lifetime. This is done by turning the
      5 version directory into a private assembly which refers to chrome_elf.dll
      6 (http://msdn.microsoft.com/library/aa374224.aspx).
      7 
      8 In an ideal world, this would be done by embedding an application config in
      9 chrome.exe that would refer to the proper version directory via a
     10 probing\privatePath attribute (http://msdn.microsoft.com/library/aa374182.aspx).
     11 This would allow us to refer to dlls in the version directory without having to
     12 make the version directory itself into an assembly. It would also avoid naming
     13 conflicts (as the WinSxS dir and GAC both take precedence over private
     14 assemblies when searching for dlls). Unfortunately, the probing\privatePath
     15 attribute is only supported for Windows 7 and later.
     16