[OpenAFS-devel] Anyone actually use any of the special build targets?

[Neulinger, Nathan]

While I am inclined to agree in some respects, that's a bit more of a change
than is suitable for the moment, and certainly not one that lends itself to
portability.

At the moment, all the changes I'm planning on making just clean up the
cruft and fine-tune the existing process. The changes also are cleaning up
and reorganizing the structure of the individual makefiles to make them
easier to eventually migrate to an automake style build, which is the
current eventual goal.

I've sent an initial small patch to Derrick to take a look at that has my
changes to a dozen or so of the Makefiles, if he doesn't find anything
blatantly disagreeable, I'll be putting together a more complete set of
changes. Some of the changes it makes should make it so that make, make all,
work properly in each dir (for the most part, but not always), and it
eliminates alot of unecessary invocations of install by tracking
dependencies for the install targets. 

-- Nathan

> -----Original Message-----
> From: eichin-oa@boxedpenguin.com [mailto:eichin-oa@boxedpenguin.com]
> Sent: Friday, August 03, 2001 2:25 PM
> To: Neulinger, Nathan
> Cc: 'openafs-devel@openafs.org'
> Subject: Re: [OpenAFS-devel] Anyone actually use any of the special
> build targets?
> 
> 
> 
> > At the very least, I want to get things to where you can 
> reasonably type
> > "make" all by itself, in any directory in src, and have it 
> do something
> > useful. 
> 
> I commend to your attention the paper "Recursive Make Considered
> Harmful", www.pcug.org.au/~millerp/rmch/recu-make-cons-harm.html, as
> an interesting way to approach this.  Requires a "modern" make, which
> turns some people off until they've actually tried it.  (There are
> some more agressive enhancements that can be pried out of one of the
> startups around here if that path interests you...)
>