Now that subconfigure don't run in parallel, we don't need to care that
their output can be interleaved, so print it out while the subconfigure
executes.
--HG--
extra : rebase_source : b7f15f18894a7e549fe4e49015d0358e9285c153
Bug 1358023 and bug 1363992 removed the last uses of subconfigure other
than js/src. We don't need all the machinery to run subconfigures in
parallel anymore.
--HG--
extra : rebase_source : f8fa050976c358834ae4a692d080c1a4105a962e
subconfigure.py shortcuts js/src/configure to avoid a msys transition
breaking the environment. But js/src/configure passes an extra
--enable-project=js that subconfigure.py currently doesn't pass.
And because in some cases, MOZ_BUILD_APP is set in the environment
(notably, in OSX universal builds, through client.mk), we need to
unset it before calling the subconfigure.
On automation, this brings Windows configure time on a clobber from 5:30 to 3:10.
Sadly, because make needs to run under intl/icu/host before configuring
intl/icu/target, intl/icu/host needs to be configured independently. Fortunately,
that's not configured for normal windows builds anyways.
Also, having multiple subconfigures sharing the same cache file is dangerously
racy. Fortunately, not a lot do. In fact, only js/src and $_subconfigure_subdir
do, so force the latter (only used for ldap sdk on comm-central) not to
configure in parallel.
While bug 903369 added some kind of wrapping, msys mangling on Windows made
it hard to make the python wrapper invoke subconfigures itself. This change
overcomes this, allowing to run subconfigures entirely independently of
the main configure if necessary, or to do more fancy checks without having
to resort to m4 and shell.
Mike Hommey
Chris Manchester