On Wed, 13 Jan 2010 15:12:40 +0100 Martin Hollmichel <[email protected]> wrote:
> Mathias Bauer wrote: > > So the only way to reuse CMake makefiles for a complete build is > > recursively calling them or - as we do today in OOo - serialize the > > process. I don't think that this is a matter of performance per se, > > it's just that the benefit is missing we wanted to get from the new > > "single make process" approach. > > > no need to have this if you have unique targets, I guess ? Mu. As long as you have a recursive build process, you have a lot of implicit dependencies and those are hurting parallelization. On top of that, process instantiation and file-I/O is very, very expensive on Windows, the slowest and most problematic platform of all (both are used extensively when doing recursion). This might not matter too much for a full build that package maintainers usually do. But it matters very much for the change->rebuild->change-cycle that devs usually do (Both implicit deps and recursion over mostly noop build tasks really hurt here). BR, Bjoern -- =========================================================================== Sitz der Gesellschaft: Sun Microsystems GmbH, Sonnenallee 1, D-85551 Kirchheim-Heimstetten Amtsgericht Muenchen: HRB 161028 Geschaeftsfuehrer: Thomas Schroeder, Wolfgang Engels, Wolf Frenkel Vorsitzender des Aufsichtsrates: Martin Haering =========================================================================== --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
