Serializing possibly resource-intensive tasks such as meinproc

[David Faure]

On Monday 11 January 2010, Lubos Lunak wrote:
> On Monday 11 of January 2010, Alexander Neundorf wrote:
> > On Friday 08 January 2010, Lubos Lunak wrote:
> > > On Thursday 07 of January 2010, Oswald Buddenhagen wrote:
> > > > a more generic solution would be recognizing a KDE4_TOOL_WRAPPER
> > > > cmake variable and prepending it to all non-c-compiler executables.
> > >  
> > >  How about the attached patch then?

Very nice.
If I understand correctly, it replaces the previous kdelibs.patch,
but icecream.patch is still needed?

> > Looks quite ok.
> > The name "KDE4_SERIALIZE_TOOL" is quite generic, but in the patch it is
> > used only for meinproc4, so this doesn't really match.
> 
>  Coolo suggested to me how to make icecream serialize only down to the
> number of CPUs instead of 1, so I can try that. In that case
> KDE4_SERIALIZE_TOOL could be used for anything people would want, although
> I myself care only about meinproc.

I often heard complaints that icecream is also launching too many "ld"
jobs on the local machine at the same time; shouldn't icecream serialize
that too, already, given that this -does- go through icecream already?
I'm a bit confused as to why ld wouldn't be serialized but meinproc
would be, somehow.

-- 
David Faure, faure at kde.org, http://www.davidfaure.fr
Sponsored by Nokia to work on KDE, incl. Konqueror (http://www.konqueror.org).