Re: Recursive make harmful

2001-06-01 Thread Alexandre Duret-Lutz
>>> "Tom" == Tom Tromey <[EMAIL PROTECTED]> writes: >> "Richard" == Richard Boulton <[EMAIL PROTECTED]> writes: Richard> You would lose the ability to build only sources in a Richard> directory and its subdirs while ignoring files they depended Richard> upon elsewhere in the tree which ar

Re: Recursive make harmful

2001-06-01 Thread Alexandre Duret-Lutz
>>> "Tom" == Tom Tromey <[EMAIL PROTECTED]> writes: [...] Tom> The idea would be to read all the Makefile.am Tom> at once and then generate a single large Makefile.in. Tom> Unfortunately I think this is very hard. We could Tom> probably do it if we could add additional constraints on Tom>

Re: AS and ASFLAGS

2001-06-01 Thread Ralf Corsepius
Tom Tromey wrote: > > > "Richard" == Richard Boulton <[EMAIL PROTECTED]> writes: > > Richard> i) Is there any documentation of this yet? I couldn't find > Richard> any, and simply had to guess what to do from error messages > Richard> and sources. > > There isn't. I'm working on docume

Re: Recursive make harmful

2001-06-01 Thread Richard Boulton
On Fri, Jun 01, 2001 at 11:16:45AM +0200, Alexandre Duret-Lutz wrote: > There is something nice about having one Makefile.am in each > subdirectory, it's that it helps to make selfcontained and > reusable modules. What is being advocated is that we keep having Makefile.am's in each separate direc

Re: Recursive make harmful

2001-06-01 Thread Alexandre Duret-Lutz
>>> "Richard" == Richard Boulton <[EMAIL PROTECTED]> writes: Richard> On Fri, Jun 01, 2001 at 11:16:45AM +0200, Alexandre Duret-Lutz wrote: >> There is something nice about having one Makefile.am in each >> subdirectory, it's that it helps to make selfcontained and >> reusable modules. Rich

aclocal: can the "duplicated macro error" be made non-fatal?

2001-06-01 Thread Dave Benson
I am working on a packaging / publishing system [1] based loosely on gnu tools (though it runs on non-gnu systems too). It's primary feature is that you can install packages from source in to a subdirectory. As a generally rule, this works nearly flawlessly, thanks principally to automake, excep

Re: Recursive make harmful

2001-06-01 Thread Eric Siegerman
On Thu, May 31, 2001 at 08:37:07PM +0100, Richard Boulton wrote: > On Thu, May 31, 2001 at 02:29:37PM -0400, Eric Siegerman wrote: > > So what *is* harmful about recursive makes (besides the admitted > > performance penalty)? > > Read "Recursive make considered harmful" > http://www.pcug.org.au/~

Re: Recursive make harmful

2001-06-01 Thread Alexandre Oliva
On Jun 1, 2001, Alexandre Duret-Lutz <[EMAIL PROTECTED]> wrote: Richard> With separate Makefile.am's in each directory, Richard> automake should be able to figure the bar/foo out from Richard> the directory paths. The user shouldn't have to worry Richard> about what the path to the top-level is

Re: AS and ASFLAGS

2001-06-01 Thread Richard Boulton
The query has come up on the automake list (okay, I raised it ;) ) about how to define AS and ASFLAGS. Until recently automake has ignored this issue, and just used CC for AS and CFLAGS for ASFLAGS. CVS automake now uses these variables, so defining them is going to become an issue for many peop

Re: automake and autoconf

2001-06-01 Thread Gary V . Vaughan
On Thursday 31 May 2001 7:47 pm, Dan Miner wrote: > Hello, Hello Dan, > I've been reading the autoconf book and I find it quite useful; however, > I've hit a wall and can't seem to wrap my head around it. Glad you like the book. > Quick layout > > proj/Makefile.am > proj/configure.in > proj/l