[prev in list] [next in list] [prev in thread] [next in thread] 

List:       wine-devel
Subject:    Re: CreateProcess design
From:       Alexandre Julliard <julliard () winehq ! com>
Date:       2002-03-31 19:23:17
[Download RAW message or body]

Eric Pouech <eric.pouech@wanadoo.fr> writes:

> what should we do. I think Alexandre long term option is to really get
> rid of the options on the command line and use the WINEOPTION(S) env
> var (we could still have a wrapper script to do the conversion)
> 
> should we adopt this right away or clean up the command line option ?

The basic idea is to have two separate programs; a 'wine' that does
all the command-line processing, and a 'wineloader' that simply
executes a new process from CreateProcess. Then all the option
handling can be moved out of kernel and into that wine program.

Winelib apps will then need to do their own command-line handling, the
kernel will simply pass them the unmodified cmdline (though it should
still be possible to launch a Winelib app through the 'wine' program
to make it handle wine options).

> as a consequence, you no longer can use any CUI program in the
> user/graphical mode, including winedbg - it still work as a unix console
> though

I've added a quick hack to fix this for now.

-- 
Alexandre Julliard
julliard@winehq.com

[prev in list] [next in list] [prev in thread] [next in thread]