This is the mail archive of the
cygwin-developers@cygwin.com
mailing list for the Cygwin project.
Re: setup.exe command line options
On Thu, 2001-11-01 at 08:58, Christopher Faylor wrote:
> On Wed, Oct 31, 2001 at 09:12:45PM -0000, Keith Starsmeare wrote:
> >
> >----- Original Message -----
> >From: "Robert Collins" <robert.collins@itdomain.com.au>
> >To: "Keith Starsmeare" <keith_starsmeare@yahoo.co.uk>
> >Cc: <cygwin-developers@cygwin.com>
> >Sent: Wednesday, October 31, 2001 9:40 AM
> >Subject: RE: setup.exe command line options
> >
> >
> >> On Wed, 2001-10-31 at 19:30, Keith Starsmeare wrote:
> >> > The arguments are passed in as one string, can I use getopt to process a
> >> > string; I imagined I that getopt worked with an array of strings i.e.
> >char
> >> > *argv[]?
> >>
> >> Fixed. I realised this just after mailing my comment :}. Update your CVS
> >> repository.
> >
> >Excellent. Thanks.
>
> I'd appreciate it if the current argv code was reverted ASAP. We can't
> use the cygwin argv stuff in setup.exe.
Why not? It's been cleanly extracted, and is (one way) GPL compatible.
> I notice that mingw has something called __argv. I wonder if that
> contains what I think it does.
>
> MSVC also has some sort of argv parser. I thought that it might be in
> msvcrt.dll but I don't know for sure.
There is a windows function, CommandlineToArgvW, but thats W char only..
> cgf