On 2015-01-14 8:37 PM, Steve Fink wrote:
On 01/14/2015 11:26 AM, Ehsan Akhgari wrote:
From now on, the only supported build mode is unified compilation. I
am planning to follow-up with removing support for the
--disable-unified-compilation configure option altogether in bug 1121000.
I commented in the bug, but I guess this is probably a better forum.
Why is the configure option being removed?
Because unsupported build configurations that are *guaranteed* to not be
maintained are not worth keeping around. I am 90% sure that
--disable-unified-compilation would have been broken since yesterday. :-)
> I understand always building
unified in automation, but not having a straightforward way at all to
see if your code is buggy seems... suboptimal. If someone wants to go
through occasionally and make our codebase valid C++, how should they do
it after this change?
Switch the UNIFIED_SOURCES variable to SOURCES in the moz.build file.
That still works.
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
