Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(479)

Side by Side Diff: chrome_elf/README

Issue 53793002: Initial implementation of Chrome Early Loading Framework (Closed) Base URL: svn://svn.chromium.org/chrome/trunk/src
Patch Set: Move elf init call back under fast notify Created 7 years, 1 month ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View unified diff | Download patch | Annotate | Revision Log
« no previous file with comments | « chrome_elf/OWNERS ('k') | chrome_elf/chrome_elf.def » ('j') | no next file with comments »
Toggle Intra-line Diffs ('i') | Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
OLDNEW
(Empty)
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.
OLDNEW
« no previous file with comments | « chrome_elf/OWNERS ('k') | chrome_elf/chrome_elf.def » ('j') | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698