make builtin dlls visible for applications?

Peter Beutner p.beutner at gmx.net
Sat Nov 19 01:48:05 CST 2005


Hans Leidekker schrieb:
> On Friday 18 November 2005 02:05, Juan Lang wrote:
> 
>>Someone proposed a hack where the loader would know that these DLLs are
>>dummies based on a wine-specific flag in the header.
> 
> Why a dummy? Why not ship a full PE DLL with a flag saying it's a built-in?
> That way file existence checks, PE header checks, LOAD_LIBRARY_AS_DATA_FILE, 
> resource scraping, even some copy protection checks, etc. could all work.

Hmm I'm not sure if you could put the linux import dependencies(from other .so libs) into
the PE header properly? So from that point of view you will never have a "fully working"
DLL file.(At least not without adding hacks to wine again to recognize these dependencies,
if put in the PE header.)

Whats the problem with LOAD_LIBRARY_AS_DATAFILE?
Otherwise I would agree with Juan that building some dummy files containing just PE header
plus maybe some sort of version info would be enough.

And iirc isn't the PE header also mapped into memory when a dll is loaded? In which case
there must be already code for that in wine(though I haven't checked that yet).

> 
>  -Hans
> 
> 
> 



More information about the wine-devel mailing list