RE: wine/ tools/runtest misc/options.c include/mod ...

[Robert Shearman]

> -----Original Message-----
> From: wine-cvs-admin(a)winehq.com [mailto:wine-cvs-admin(a)winehq.com]On
> Behalf Of Alexandre Julliard
> Sent: 25 September 2003 21:34
> To: wine-cvs(a)winehq.com
> Subject: wine/ tools/runtest misc/options.c include/mod ...
> Removed the --dll option and replaced it by the WINEDLLOVERRIDES
>   environment variable.

This will break a lot of HOWTOs on various sites that describe how to get
apps working with Wine.
Can we not have some period of time where we can use both methods and maybe
remove the --dll option later (say when winecfg is ready)?

Rob

wine/ tools/runtest misc/options.c include/mod ...

[Alexandre Julliard]

"Robert Shearman" <R.J.Shearman(a)warwick.ac.uk> writes:
> This will break a lot of HOWTOs on various sites that describe how to get
> apps working with Wine.

I don't see why, the HOWTOs should explain how to set dll overrides in
the config file, that has been the standard way for a long time now.

-- 
Alexandre Julliard
julliard(a)winehq.com

wine/ tools/runtest misc/options.c include/mod ...

[Mike Hearn]

On Thu, 2003-09-25 at 22:06, Alexandre Julliard wrote:
> "Robert Shearman" <R.J.Shearman(a)warwick.ac.uk> writes:
> > This will break a lot of HOWTOs on various sites that describe how to get
> > apps working with Wine.
>
> I don't see why, the HOWTOs should explain how to set dll overrides in
> the config file, that has been the standard way for a long time now.

For doing things like InstallShields etc, it's common practice for
people to be given canned command lines, such as 

wine --dll ole32,oleaut32,rpcrt4=n myprog.exe

basically because this is more convenient than altering the config file
for each combination. I guess

WINEDLLOVERRIDES="ole32,oleaut32,rpcrt4=n" wine myprog.exe

is only slightly longer. 

Why must wines command line options be removed though? They are often
handy for testing things out.

thanks -mike

wine/ tools/runtest misc/options.c include/mod ...

[Alexandre Julliard]

Mike Hearn <mike(a)theoretic.com> writes:
> Why must wines command line options be removed though? They are often
> handy for testing things out.

They break dll separation, and they interfere with the command line of
Winelib apps. It's easy enough to write a wrapper script to handle
options if you want them, but there are cases where you don't want
them, so the Wine kernel must not impose a specific command line
parsing, this should be left to the higher layers.

-- 
Alexandre Julliard
julliard(a)winehq.com