Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <0b1901c227a0$b4c0a590$2300a8c0@LAPTOP>
From: "Robert Collins" <robert DOT collins AT syncretize DOT net>
To: <cygwin AT cygwin DOT com>
References: <000301c226b5$6dec3d50$a701a8c0 AT earthlink DOT net> <200207092316 DOT 58319 DOT rasjidw AT openminddev DOT net> <3D2B092F DOT 1030606 AT ece DOT gatech DOT edu>
Subject: Re: Problem with cygwin1.dll and xfree
Date: Wed, 10 Jul 2002 09:31:09 +1000
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000


"Charles Wilson" <cwilson AT ece DOT gatech DOT edu> wrote in message
news:3D2B092F DOT 1030606 AT ece DOT gatech DOT edu...

> > I think that basically what would be required would be to enable
Setup.exe to
> > be controlled by a config file (similar to a RedHat kickstart file), and
have
> > its GUI not displayed unless there was a problem and user interaction
was
> > required.
..
> This is a good idea -- and the skeleton is already there.  What you need
is
>    1) first, command-line options that can completely control setup's
> behavior from start to finish.  Robert wrote and entirely separate
> GPL'ed option handler in OO C++ (all existing getopt/popt
> implementations are C, or C-dressed-up-as-C++).  There are even a few
> commandline options already implemented.  It just needs fleshing out

Yup. And the majority are trivial to add. The list-of-packages-to-install
collection is the (slightly) hard one as GetOpt++ has no 'native' interface
for that at the moment. However I've implemented such a collection twice now
using GetOpt++ for other projects, and am about ready to provide a generic
interface in GetOpt++.

>    2) Then, add the ability to read all of those options from a config
> file, including pkgs-to-install.  (This may actually already exist as
> part of Roberts GetOpt++ project)

It's not a deliberate inclusion, but consider that a command collection
takes argc, argv arguments. Parse the file into strings, treating unquoted
spaces and line breaks as new strings. Place pointers to those cstrings in a
vector and it's all done.

Rob


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/