WINEDLLPATH and /usr/lib/wine

Hin-Tak Leung hintak_leung at
Tue Jan 26 10:10:04 CST 2010

--- On Tue, 26/1/10, Ben Klein <shacklein at> wrote:

> For DLLs at least, you should be able to rename the
> to a .dll
> and stick it in the application's directory. I don't recall
> the last
> time I tried this, but it certainly worked (I was using a
> hacked
> to get Diablo and Worms Armageddon playing
> nicely). I
> assume you could do something similar for EXEs.

Thanks for the tips - that sounds a bit wrong though, so's are not PE dll's :-). It is a nice hack and probably should/could be documented somewhere.

> Is there some specific reason why you *need* WINEDLLPATH to
> override
> standard built-ins? Is your being called by some
> other
> process that does not specify the full path, or something
> along those
> lines?

ddiwrapper (doing printing using vendor dll) uses a hacked-up gdi32 to receive bitmaps from the host's ghostscript to feed to the vendor printing dll. I didn't write the code - this is my understanding of how it works.  


More information about the wine-devel mailing list