Frank wrote:
Heck, what machine are you compiling on? :) Recompiling all of, say, dbaccess or connectivity or svtools or svx or extensions (modules where I usually work) takes *much* longer (at least on Windows), and they are smaller than sc.
Here are the results from the first prototype (just to repost the link) http://go-oo.org/tstooo/build_prototype_paper.pdf The measurements are from a local build on a pretty standard workstation (and -j1). sc compiles in about 8 minutes from scratch (and I think I have a few tricks to optimize this further). Some of the lower level modules are also significantly faster. This also includes a tentative profile of the build.pl/dmake system and a breakdown of where the speed is coming from (Heiner). still Frank:
(and I'm talking about Windows local builds only. Building a Windows OOo on a network machine takes *days*! With complete dependencies, this is more likely to hit us ...)
I have been thinking about this for a while, and nothing stops us from providing a Sun network, nodep, deliver/solver based build (essentially the current system including some of the speed increases). You could then optionally turn on deps, single build directory and all the other goodies in case you are building on a local machine.. Compatibility or speed .. :-) It seems like we all agree we need practical tests to see how things work out. I'm officially on holiday this week, so I'll get back on this during next week. After that my plan is to do weekly releases of the proto (probably as a download, a CWS and part of ooo-build), to get early feedback from everyone. At this stage I'd like to remind everyone we are still testing this stuff, this will mostly not be good enough for production work! Take care, Kai -- Kai Backman, Software Engineer, [EMAIL PROTECTED]
