setup changes to build standalone

[Robert Collins]

> -----Original Message-----
> From: Jan Nieuwenhuizen [mailto:janneke@gnu.org] 
> Sent: Friday, April 26, 2002 6:19 PM
> To: cygwin-apps@cygwin.com
> Subject: Re: setup changes to build standalone
> 
> 
> "Robert Collins" <robert.collins@itdomain.com.au> writes:
> 
> > Heh. The main things I get from automake is
> > a) make dist. I _love_ this so much it ain't funny.
> 
> If you're willing to depend on gnu make features, make dist 
> is no rocket science.

Sure. I'm not relying on gnu make features though. Also make dist-all
while again, not rocket science, is very useful. And I'm -sure- that its
more that 1 line to create that for each package.
 
> Because of the horrors of automake, we've implemented a sane 
> set of make rules, mainly for LilyPond, that has all these 
> features and allows

I'll have a look at some point. I actually find automake much less
horrible that doing everything by hand. Anyway, this is off-topic here -
unless you are objecting to setup being automakified?
 
> > e) non-recursive makefiles of a reasonable size.
> 
> a make file for a library or executable typically about 10 lines long.

Ermm, most of my projects have much more than 10 lines just listing the
source. (And before you bring up wildcards, I don't like them and
wouldn't use them even if they where available in automake. I like
knowing exactly what is in the package.)

Rob