cmake and progress reporting

Thiago Macieira thiago at kde.org
Fri Jun 16 08:30:03 BST 2006


Alexander Neundorf wrote:
>so can somebody with access to a build farm please test current cmake
> cvs HEAD which features progress reporting and measure whether it slows
> down parallel builds ?

Here are the results.

3 times with cmake 2.4.2 (no progress reporting):
530.02user 109.99system 13:19.17elapsed 80%CPU (0avgtext+0avgdata 
0maxresident)k
539.02user 149.10system 18:03.99elapsed 63%CPU (0avgtext+0avgdata 
0maxresident)k
528.20user 110.76system 13:00.81elapsed 81%CPU (0avgtext+0avgdata 
0maxresident)k
build succeeded in all 3 attempts

With cmake CVS (with progress reporting):
426.31user 108.78system 11:34.65elapsed 77%CPU (0avgtext+0avgdata 
0maxresident)k

But the build failed (I tried more than once)

-- 
Thiago Macieira  -  thiago (AT) macieira.info - thiago (AT) kde.org
  thiago.macieira (AT) trolltech.com     Trolltech ASA
    GPG: 0x6EF45358                   |  Sandakerveien 116,
    E067 918B B660 DBD1 105C          |  NO-0402
    966C 33F5 F005 6EF4 5358          |  Oslo, Norway
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 191 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20060616/eb45a203/attachment.sig>


More information about the kde-core-devel mailing list