On Mon, Feb 23, 2009 at 6:15 AM, Paul Vriens paul.vriens.wine@gmail.com wrote:
The reason you see this is because next to a normal LoadLibrary we also use the .NET variant. On some boxes gdiplus.dll cannot be found through LoadLibrary but will trough LoadLibraryShim. As winetest now thinks the library is there it will try to launch "gdiplus_test.exe --list" and that of course fails.
Not sure how to approach this.
Silly question:
Could we, if LoadLibraryShim returns a library that isn't in the PATH, add it to the PATH in the environment used to call the test exe? Then we would be able to run tests on some "new" versions of dll's we can't cover currently.