Hin-Tak Leung wrote:
I asked about the same problem a while ago without any response, but
I have a patch for it:
https://www.linuxfoundation.org/en/User:Htl10#Ddiwrapper_.28a.k.a._.22Using_Vendor_win32_printer_driver_in_Linux.22.29
I can see how that patch would work. Though I can also see why it
wouldn't be accepted! :) I'll let you know if I come up with something
else that doesn't need a patch - though I am not hopeful.
Thanks ... mo
I reckon it is because the wine devs don't want people to override
certain things. WINEDLLPATH used to work until Feb/March 2006 .
--- On Mon, 25/1/10, Michael Ost <[email protected]> wrote:
Hi,
I am wanting to direct wine to launch a specific APP.exe.so program
by using WINEDLLPATH during the development of APP.exe.
Unfortunately (and undocumented-ely if you know what I mean)
WINEDLLPATH is superseded by /usr/lib/wine. So if
/usr/lib/wine/APP.exe.so exists, WINEDLLPATH will find that one
instead of the one I am trying to target.
So, if these files exist: /usr/lib/wine/APP.exe.so
/MY_DIR/APP.exe.so
Then this command... WINEDLLPATH=MY_DIR wine APP.exe ... will start
/usr/lib/wine/APP.exe.so and not /MY_DIR/APP.exe.so.
Is this on purpose? It doesn't seem right at first glance. I would
assume that WINEDLLPATH would take precedence. Otherwise what
purpose would it serve?
Thanks for tips or background, Michael Ost Muse Research, Inc.
