Apologies on the delayed reply, but I felt like taking the bait..
I respectfully and fully disagree that running make in a subdirectory is
admission of anything other than a need to clean some a subset of a given
project in a convenient manner. The reason someone might want to do a make
clean
Hi all,
Bob Friesenhahn wrote:
> On Mon, 29 May 2006, Stefan Puiu wrote:
>> However, people haven't mentioned yet the main point in Peter Miller's
>> paper - dependency handling, which I think is very important (I would
>> say significantly more important than the ability to type "make clean"
>>
Hi,
On 6/6/06, Ralf Corsepius <[EMAIL PROTECTED]> wrote:
Well, that's one of those cases I'd prefer to call "urban legends" of
"flat makefiles".
Yes, in an ideal world, a flat makefile can take all dependencies. But
in real world a complex package consists of more or less independent
subpackage
On Tue, 2006-05-30 at 12:23 -0500, Bob Friesenhahn wrote:
> On Mon, 29 May 2006, Stefan Puiu wrote:
> > However, people haven't mentioned yet the main point in Peter Miller's
> > paper - dependency handling, which I think is very important
Well, that's one of those cases I'd prefer to call "urban l
On Mon, 29 May 2006, Stefan Puiu wrote:
However, people haven't mentioned yet the main point in Peter Miller's
paper - dependency handling, which I think is very important (I would
say significantly more important than the ability to type "make clean"
in one directory). Most people I work with ar
> "Ralf" == Ralf Corsepius <[EMAIL PROTECTED]> writes:
Ralf> An aspect, I don't see how an import feature would help is
Ralf> "scoping": A subdir-Makefile.am controls one subdir, a flat
Ralf> toplevel Makefile controls all subdirs. I.e. when developing on
Ralf> a package, with a non-flat Makef
HI all,
I find some of the information in this thread quite useful, especially
since I was considering to move some of our project files to
non-recursive makefiles. I understand the downsides - silly variable
names in subdir makefiles, which are also tied to the respective
directory and require
On Wed, May 24, 2006 at 01:57:15PM +0200, Ralf Wildenhues wrote:
> * Olly Betts wrote on Wed, May 24, 2006 at 12:24:53PM CEST:
> > * Generally, it would be useful for the manual to go into a bit more
> > detail about how to approach all this.
>
> Agreed. I'm sure Alexandre will gladly accept co
On Wed, 2006-05-24 at 13:57 +0200, Ralf Wildenhues wrote:
[snip..]
- Non-recursive makefiles are suitable for projects of mediocre
complexity. For complex projects the price of flat Makefile is high
and
often doesn't pay off.
Hear hear! After spending a fair bit of time considerin
On Wed, 2006-05-24 at 17:01 +0200, Ralf Wildenhues wrote:
> * Ralf Corsepius wrote on Wed, May 24, 2006 at 04:34:02PM CEST:
> It often helps a lot to have fewer Makefiles than one per directory,
> especially in parts of a source tree where they are rather simple.
>
> > - subdir makefile.am-fragme
* Ralf Corsepius wrote on Wed, May 24, 2006 at 04:34:02PM CEST:
>
> - Non-recursive makefiles are suitable for projects of mediocre
> complexity. For complex projects the price of flat Makefile is high and
> often doesn't pay off.
Yes, agreed as well, but I think nobody is su
On Wed, 2006-05-24 at 13:57 +0200, Ralf Wildenhues wrote:
> Hi Olly,
>
> * Olly Betts wrote on Wed, May 24, 2006 at 12:24:53PM CEST:
> > I've been looking at the feasibility of converting a project (Xapian)
> > using autoconf+automake+libtool to using non-recursive make
On Wed, 24 May 2006, Olly Betts wrote:
* I'm not sure what to call the Makefile.am snippets in the
subdirectories. I looked at GraphicsMagick which was suggested to be
Likewise. :-)
harder to maintain. It'd be really handy to have a way to
automatically prepend the directory that the cu
Hi Olly,
* Olly Betts wrote on Wed, May 24, 2006 at 12:24:53PM CEST:
> I've been looking at the feasibility of converting a project (Xapian)
> using autoconf+automake+libtool to using non-recursive makefiles.
> I'm fairly convinced it'll be an improvement overall, but
I've been looking at the feasibility of converting a project (Xapian)
using autoconf+automake+libtool to using non-recursive makefiles.
Currently each subdirectory produces a libtool convenience library
and these are linked into the main installable library. There are
a few conven
15 matches
Mail list logo