This is the mail archive of the
cygwin-apps@cygwin.com
mailing list for the Cygwin project.
Re: libgetopt++ and setup and libstdc++
- From: Earnie Boyd <earnie_boyd at yahoo dot com>
- To: Robert Collins <robert dot collins at itdomain dot com dot au>
- Cc: Cygwin-Apps <cygwin-apps at cygwin dot com>
- Date: Sat, 27 Apr 2002 11:13:00 -0400
- Subject: Re: libgetopt++ and setup and libstdc++
- References: <FC169E059D1A0442A04C40F86D9BA7600C5F24@itdomain003.itdomain.net.au>
- Reply-to: Earnie Boyd <Cygwin-Apps at Cygwin dot Com>
Robert Collins wrote:
>
> Ok,
> we're finally there. Setup now can use libstdc++ routines,
> allowing the full range of C++ programming constructs. Probably even
> exceptions, but I have not tested that yet.
>
> I've removed the half-done GetOption.cc and GetOption.h from setup, they
> are part of libgetopt++, which is a much easier tool for options.
>
> *** IMPORTANT ***
> libgetopt++ does not store the autotool created files in CVS. You'll
> need to run ./bootstrap.sh in it's source dir to create them.
> *****************
>
That's goes against the FSF standard and the recommendations of the
autotools groups themselves. You shouldn't require the user to have the
autotools installed. That's the reason every package always has all of
the needed files for configure to execute.
Earnie.