Re: Tracing where build time is spent

On Tuesday 18 of February 2020, Stephan Bergmann wrote:
> You left it somewhat unclear what the target audiences for your various
> performance improvement proposals are (local builds, Gerrit Jenkins
> builds, other tinderbox builds, "official" TDF release builds, ...).

 I assumed it was implied where it mattered. Using --enable-debug/dbgutil is 
for developer builds, isn't it?

> Using --enable-python=system for Gerrit Jenkins builds would trade
> significance of those builds ("will a release build with this change be
> good?") for build performance.

 Strictly speaking, no Jenkins build does that except for the Linux GCC 
release one, as all the others build with --enable-dbgutil, so I find this 
argument weak. In practice it seems it's the tinderboxes that check this (if 
at all).

-- 
 Luboš Luňák
 l.lunak@collabora.com