Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm Sender: cygwin-apps-owner AT cygwin DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Mail-Followup-To: cygwin-apps AT cygwin DOT com Delivered-To: mailing list cygwin-apps AT cygwin DOT com Message-ID: <3CCABFFC.34322E90@yahoo.com> Date: Sat, 27 Apr 2002 11:13:00 -0400 From: Earnie Boyd Reply-To: Earnie Boyd X-Accept-Language: en MIME-Version: 1.0 To: Robert Collins CC: Cygwin-Apps Subject: Re: libgetopt++ and setup and libstdc++ References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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.