participants: Ause, Kai Backmann, Michael Bemmer, Stephan Bergmann, Nils Fuhrmann, Martin Hollmichel, Matthias Huetsch, Heiner Rechtien, Juergen Schmidt.

Kai B. provided some information about his investigation in the OOo build System. The main thesis he presented was that the overall build time of OOo is too high at this moment and that we need to reduce this time to attract more developers to step into OOo build.

Michael Bemmer pointed out, that there is an agreement that lowering the barriers of entrance for contributing code to OOo is in very important topic for the project.

Kai B. presented his analysis that about
33 % of overall build time is compiling C/C++ Files
27 % of the build time is needed by dmake/build tools
22 % of the time is needed for generating files dependencies.

concentrating efforts for improvement to build system, especially wrt dependencies might have best results. Kai gave an introduction into jam which is an build tool which handles dependencies quite efficient. He also presented performance data about his jam build protoype for OOo which looked quite promising.

additional technics like the usage of precompiled header files and batched compiling for several C++ files at once gives addtional speed up so that an build e.g. for Calc gives a speedup of more than factor 2.

ause and Heiner argued that the configuration of the build environment could be tweaked at some places, so that the usage of dmake will lead to better results (technical details will be discussed on [email protected]).

next steps:

* validations of the hot spots of the build system with different configuration of build environment and other optimizations; Kai will provide the modified tools for measuring this.

* analysis of "why is mozilla compiling each line of code about four times faster than OOo ?"

* review and feedback of jam prototype by Ause

* Martin H. will set up follow up meeting right after OOo conference.

Martin

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to