Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com content-class: urn:content-classes:message Subject: RE: setup.exe command line options MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Date: Thu, 1 Nov 2001 12:07:49 +1100 X-MimeOLE: Produced By Microsoft Exchange V6.0.4417.0 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: setup.exe command line options Thread-Index: AcFibHkMgj3Bz5N3Txuiv6WniGYA7gABPd3g From: "Robert Collins" To: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id fA1103u08758 > -----Original Message----- > From: Christopher Faylor [mailto:cgf AT redhat DOT com] > Sent: Thursday, November 01, 2001 11:24 AM > To: cygwin-developers AT cygwin DOT com > Subject: Re: setup.exe command line options > > > On Thu, Nov 01, 2001 at 10:00:23AM +1100, Robert Collins wrote: > >> 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. > > We've tried (or at least I've tried) to keep the two source bases > separate. If random bits of cygwin, which we care about, > start showing > up in other projects that we really don't care about then it is just > more of a headache to keep track of. Sure, however I figured that as setup.exe's needs are much more modest it would be a one way export, with no need for further changes. (The one I put there is somewhat simpler than the orginal cygwin one. > Then there is also the technical reason that we don't need it since > __argv seems to do what we need automatically. Just include stdlib.h > and you have the parsed command line available. Cool. I'll look into this and backout the change once I've got it working. Rob