On 23/09/2016 11:20, Ted Mielczarek wrote:
On Fri, Sep 23, 2016, at 05:58 AM, Panos Astithas wrote:
I used to do that in the past, but nowadays artifact builds have changed
the cost-benefit trade-off so very few people bother AFAIK, when not
touching C++ code. If we could get artifact builds to use --enable-debug
and --enable-optimize (or have an option to do so) that could change the
calculus.
The debug builds we do in automation are already built with optimization
(we changed this a few years ago to speed up running tests), so it ought
to be straightforward to make debug artifact builds work by fetching
those bits.
-Ted
Then this enables me to answer Ehsan's question. These are the builds
I've recently tried using (e.g. when debugging intermittents in VMs
because then I don't need to set up too much of a build env) and they're
still very slow.
You can use debug builds from artifact mode using the MOZ_DEBUG switch
in your mozconfig (see
https://bugzilla.mozilla.org/show_bug.cgi?id=1253697 - annoyingly, last
I tried, just --enable-debug isn't good enough to download debug bits,
see also the patch that landed for that bug).
~ Gijs
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
