Robert van Herk robert@robertvanherk.nl writes:
This is a patch that adds a tabsheet to winecfg, that allows the user to change the dll overrides; both globally and per app.
I put this in, but note that there are more possibilities that just builtin or native that will have to be supported too. Altogether there are five possible combinations: "builtin", "native", "builtin,native", "native,builtin", "".
Alexandre Julliard wrote:
So what would each one mean? I looked in the documentation on http://www.winehq.com/site/docs/wine-user/config-dll, but cannot find any details.
Let me get this straight: dll overrides specificy whether you want to use the windows dll or wine dll, right? So, when you put it on "", this is essentially the same as leaving the dll override out?
And how is "native" different from "native, builtin"? Will Wine refuse to load the dll at all, when it's configured to use a native dll and it cannot find one?
And do you really think the user should be troubled by having these 5 options? After all, we wanted to keep winecfg simple, not complete, right?
Greetings, Robert
No. Leaving the DLL override out will make Wine use the default override policy. Specifying "" means that Wine shouldn't load that library. In other words, a disable option. It is occasionally useful for setup programs, like the DCOM one that won't install if one of the Wine DLLs is present.
Yes.
And do you really think the user should be troubled by having these 5 options? After all, we wanted to keep winecfg simple, not complete, right?
I think you could make it quite simple. Just have six options: o Use default override setting o Use Wine built-in always o Try loading Wine built-in first, then if not present, Windows native o Try Windows native first, then if not present Wine built-in o Use Windows native always o Disable this DLL
Rob
-
Alexandre Julliard -
Robert Shearman -
Robert van Herk