On Sat, Mar 24, 2007 at 09:47:00AM +0100, Peter Kümmel wrote: > Andre Poenitz wrote: > > More data, mathed this time. > > > > 'Lumped' means a Mathed.C #include'ing everything else. > > > > Times are real/user/sys. > > > > Now Lumped > > > > Null build 2.6/1.4/0.9 1.6/1.3/0.3 > > > > Full rebuild 154/132/12 48/ 44/ 1 > > > > change MathParser.C 12/1.5/1 48/ 44/ 1 > > > > So lumping everything together buys more than 30% in the common case of > > a Null and 60% for Full builds. The downside is when actually _working_ > > on single files in mathed, where there's an increas of 300%. > > We could introduce a mechanism to manually remove some files from the > lumped files. Then one has the lumped files for all the untouched code > and a handfull files which will be compiled separate. > > Any ideas for this 'mechanism'?
Not on the preprocessor level working for all build system. Of course, we could have a file 'WorkSet' somewhere in the build tree containing names of files one is working on and the build mechanism lumps everything together apart from the files listed. I certainly could set up something like that using GNU make, but I can't handle autotools. The 10...20 files/lump approach OTOH has the special charm that it works independent of the build system within the language. Andre' PS: How's "Bordmittel" translated into English?
