Harlan Stenn <[EMAIL PROTECTED]> writes:
> While it is "too late now" for this round of GSoC, it might be a really
> amazing idea to have somebody work on a project to:
>
> - make sure automake has all the needed bits to produce useful
> non-recursive Makefiles
> - demonstrate how easy it is to
On Thu, 10 Apr 2008, Harlan Stenn wrote:
While it is "too late now" for this round of GSoC, it might be a really
amazing idea to have somebody work on a project to:
- make sure automake has all the needed bits to produce useful
non-recursive Makefiles
- demonstrate how easy it is to set this u
Bob Friesenhahn wrote:
> Setting up a non-recursive build project with Automake would not be
> such a chore if Automake knew how to ingest per-subdirectory Makefiles
> into the overall build, adding any necessary path information. The
> biggest chore related to setting up a non-recursive build
On Thu, 10 Apr 2008, Ralf Wildenhues wrote:
I've thought of this, in fact just a couple of weeks ago. It is
possible to formulate SUBDIRS rules in a way that allows parallel
execution of the sub makes (by something like turning each subdir
into a target). However, doing so by default will cert
Hi Bob,
* Bob Rossi wrote on Thu, Apr 10, 2008 at 03:28:56PM CEST:
> I currently have my project setup so that each subdirectory has a
> Makefile.am. I've noticed that when I do 'make -j4' that it does 1
> directory at a time, then links a little library or makes a program.
>
> If I moved everyth
On Thu, 10 Apr 2008, Bob Rossi wrote:
If I moved everything to a single Makefile.am at the top level, would
that improve the speed of things so that it could continue to build
in parallel?
Yes. If you convert your project to a non-recursive build, then it is
very likely that considerably mor
