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 Subject: RE: setup changes to build standalone MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Fri, 26 Apr 2002 17:17:03 +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: "Gary R. Van Sickle" , "Cygwin-Apps" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id g3Q7JDO08043 > -----Original Message----- > From: Gary R. Van Sickle [mailto:g DOT r DOT vansickle AT worldnet DOT att DOT net] > Sent: Friday, April 26, 2002 2:25 PM > > On a separate but related topic, I'd like to automakeise (is that a > > word) setup - if there are no objections from the other > contributors. > > No, on the contrary I think that's a great idea. Raw > Makefile.in's scare the hell out of me. ;-) Heh. The main things I get from automake is a) make dist. I _love_ this so much it ain't funny. b) all the 'stock' rules - so that things like make clean _always_ hit all subdirs etc etc. c) consistent VPATH support. d) multicompiler dependencies (not that I personally use it much, I'm gcc most everywhere) e) non-recursive makefiles of a reasonable size. Makefile.in's aren't good or bad in raw form IMO. Rob