http://bugs.winehq.org/show_bug.cgi?id=21778
Sam Morris sam@robots.org.uk changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |UNCONFIRMED Resolution|INVALID |
--- Comment #2 from Sam Morris sam@robots.org.uk 2010-02-20 09:21:29 --- This is not ideal because then I can't have several builders run the tests with different versions of the depended-upon DLLs. It is also inconvenient as I'm not sure how to edit the registry without having to run regedit, which does not work on a system without a GUI.
If I were building in a native Windows environment, I would be able to modify the test scripts to set the PATH environment variable before the test executables are launched; this works because the test scripts are themselves run in the Windows environment. But with Wine, this is not possible, because the test scripts are external to the existence of the Windows environment--hence my wish for there to be some way to modify Wine's behaviour at launch. Modifying the environment by editing the registry is not ideal because it's not something that the build system can do (it doesn't know about Wine, it just launches the built executables as it would on any other operating system) and because it is a permanent change that would affect other concurrent test runs.
I'm reopening the bug because I think I have a use case, without acceptable workarounds, that would be shared by others who might try to use Wine to perform automated tests of software built in a cross-compilation environment.
If this is really something that you will never consider implementing then you can close it again.