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 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: RE: libgetopt++ and setup and libstdc++ Date: Sun, 28 Apr 2002 03:31:45 +1000 X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Robert Collins" To: "Earnie Boyd" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id g3RHVmW19744 > -----Original Message----- > From: Earnie Boyd [mailto:earnie_boyd AT yahoo DOT com] > > *** 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. Perhaps I wasn't clear. This is only for CVS. Distributions and -src packages will naturally have the autotool generated files included. However, CVS is _not_ a distribution, and anyone developing from CVS will require the autotool suite if they make any non-trivial changes. That's part of why AM_MAINTAINER_MODE exists, and what 'make dist-all' is for. If I was clear, and you still think CVS should have those files... http://sources.redhat.com/autobook/autobook/autobook_43.html#SEC43 paragraph 4. The bootstrap recipe is what I follow, and it's been very reliable and easy to use on several projects. Rob