On Tue, 2003-12-02 at 02:10, Bob Friesenhahn wrote:
> > Hmm, I'd prefer to do it via the include mechanism - see my crude, but
> > effective updated proof of concept - posted here a minute ago.
> 
> I like your include approach.  It helps convert existing recursive
> builds into non-recursive builds with minimum pain.  However, there
> are sufficient reasons to write only one Makefile (e.g. source tree is
> treated as "read only", or personal preference) that both mechanisms
> should be supported.

I'm not arguing against the single-big-file-method... but I am curious:
how does a 'read only' source tree affect this? If there is a
Makefile.am in it that you want to use without alteration, you can just
SUBDIRS= x y z   #not subdir
DIST_SUBDIRS=x y z subdir
subdir_include subdir/Makefile.am

Rob

-- 
GPG key available at: <http://www.robertcollins.net/keys.txt>.

Attachment: signature.asc
Description: This is a digitally signed message part

Reply via email to