On Tuesday September 25 2007 03:31, Kuang-Chun Cheng wrote: > Hi, > > I test both 0.9.44 and 0.9.45 and found that Wine does not use > PATH environment variables for DLL search. > > My test application is a Qt 336 application, QSlider.exe. > QSlider.exe require both qt-mt336.dll and mingwm10.dll. If I copy > both dll to ~/.wine/drive_c/windows/system32, I can invoke QSlider.exe > from anywhere and it works OK. > > If I put both dlls to, eg. /opt/qt-3.3/bin. And setup PATH with > /opt/qt-3.3/bin included. Invoke QSlider.exe will give me error message: > > err:module:import_dll Library qt-mt336.dll (which is needed by > L"Z:\\home\\kcc\\QSlider.exe") not found > err:module:LdrInitializeThunk Main exe initialization for > L"Z:\\home\\kcc\\QSlider.exe" failed, status c0000135 > > My guess is wine just simple ignore PATH environment variable when > searching DLL, > am I correct ? Is this a bug or a feature ? > Under WinXP/2K ... the PATH env. variables do work ... but not Wine. > Can someone confirm this ? Thanks a lot. WINE use PATH variable in the registry. Of course environment variable is a different thing. In Windows you don't use Linux environment variables and Linux shell (this is obvious): you are using cmd instead. WINE is no different so to get access to WINE environment you need to run this: wine cmd And now type this: PATH You will see current PATH environment variable. I didn't test it but I guess it will work correctly if you change it (if not this is a real bug). To me it seems that you confuse Windows cmd environment with Linux shell environment. Here is an example: % echo $PATH /usr/local/kde/bin:/usr/local/bin:/usr/local/sbin:/usr/bin:/bin:/usr/bin/X11:/usr/games:/sbin:/usr/sbin:/usr/games:/usr/share/lg3d/bin:/opt/maxwell64 % wine cmd CMD Version 0.9.45 Z:\var\pkgs\nvidia>PATH PATH=c:\windows\system32;c:\windows _______________________________________________ wine-users mailing list wine-users@xxxxxxxxxx http://www.winehq.org/mailman/listinfo/wine-users
