This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Suggestions for improving gcc 3.2 compilation speed?
- From: Michael Matz <matz at suse dot de>
- To: Zack Weinberg <zack at codesourcery dot com>
- Cc: "Kaveh R. Ghazi" <ghazi at caip dot rutgers dot edu>, <awinkler at maad dot com>,<gcc at gcc dot gnu dot org>
- Date: Mon, 17 Mar 2003 15:34:27 +0100 (CET)
- Subject: Re: Suggestions for improving gcc 3.2 compilation speed?
Hi,
On Fri, 14 Mar 2003, Zack Weinberg wrote:
> 'Recursive Make Considered Harmful', Peter Miller. Abstract, and link
> to full text, at
> <http://www.tip.net.au/~millerp/rmch/recu-make-cons-harm.html>.
<shameless plug>
Use unsermake (KDE CVS, kdenonbeta/unsermake). Its input files resemble
automake Makefile.am's (so it's not that difficult to "port" existing
projects to it), but it creates a Makefile hierarchy including the whole
tree (including inter-directory dependencies) which is then processed by
one make from the toplevel. A parallel make on this tree is _much_ faster
than with automake (because it's parallelism is limited to one directory).
For KDE with a compile server in the back it's extremely usefull.
</shameless plug>
It has some issues with sub-directory configures, but is Good Enough (TM)
for us ;-)
Ciao,
Michael.