Re: Build times of different projects

On 8/26/13 6:31 PM, Mike Hommey wrote: Not necessarily. You can take that as being exactly the point being made, and it has some value. If your preprocessed source is 40 times bigger than the plain source, there might be something wrong. Mmm... We pretty commonly have files whose .i is 40x big

Re: Build times of different projects

On Mon, Aug 26, 2013 at 06:23:09PM -0400, Ehsan Akhgari wrote: > On 2013-08-26 6:16 PM, Mike Shal wrote: > >On 08/25/2013 12:05 PM, Ehsan Akhgari wrote: > >>Note that the code itself (and not just its size) being compiled can also > >>change the compilation time, as the compiler needs to perform th

Re: Build times of different projects

On 2013-08-26 6:16 PM, Mike Shal wrote: On 08/25/2013 12:05 PM, Ehsan Akhgari wrote: Note that the code itself (and not just its size) being compiled can also change the compilation time, as the compiler needs to perform things such as template instantiation, Koenig name look-ups, etc. Those fa

Re: Build times of different projects

On 08/25/2013 12:05 PM, Ehsan Akhgari wrote: > Note that the code itself (and not just its size) being compiled can also > change the compilation time, as the compiler needs to perform things such > as template instantiation, Koenig name look-ups, etc. Those factors will > not change by reducing t

Re: Build times of different projects

Note that the code itself (and not just its size) being compiled can also change the compilation time, as the compiler needs to perform things such as template instantiation, Koenig name look-ups, etc. Those factors will not change by reducing the #include dependencies. Cheers, -- Ehsan

Build times of different projects

Hi, I just read this: http://voices.canonical.com/jussi.pakkanen/2013/08/23/comparing-build-speeds-of-different-code-bases/ The author compiled 10 different C++ projects and found that the number of lines compiled per second varied from 46 to 288. The final paragraph: "What we can deduce from