Problem with cygwin1.dll and xfree

Robert Collins robert.collins@syncretize.net
Tue Jul 9 16:56:00 GMT 2002


"Charles Wilson" <cwilson@ece.gatech.edu> wrote in message
news:3D2B092F.1030606@ece.gatech.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/



More information about the Cygwin mailing list