mirror of
https://github.com/mozilla/gecko-dev.git
synced 2024-11-01 14:45:29 +00:00
69e70086e0
Before, we would run configure in both top-level and js/src, and both configures would traverse their own set of moz.builds, without actual knowledge about the other. With this change, both configures still run, but only top-level traverses moz.build files, and uses js/src's config.status when traversing its moz.build files. This allows a better sharing of information between both build systems and the removal of many hacks. This also moves running libffi and icu configure to top-level. Standalone js builds still have their own configure doing moz.build traversal, as before. --HG-- rename : config/autoconf.mk.in => config/autoconf-js.mk.in rename : config/emptyvars.mk.in => config/emptyvars-js.mk.in
26 lines
1.1 KiB
Plaintext
26 lines
1.1 KiB
Plaintext
# To Trigger a clobber replace ALL of the textual description below,
|
|
# giving a bug number and a one line description of why a clobber is
|
|
# required. Modifying this file will make configure check that a
|
|
# clobber has been performed before the build can continue.
|
|
#
|
|
# MERGE NOTE: When merging two branches that require a CLOBBER, you should
|
|
# merge both CLOBBER descriptions, to ensure that users on
|
|
# both branches correctly see the clobber warning.
|
|
#
|
|
# O <-- Users coming from both parents need to Clobber
|
|
# / \
|
|
# O O
|
|
# | |
|
|
# O <-- Clobber O <-- Clobber
|
|
#
|
|
# Note: The description below will be part of the error message shown to users.
|
|
#
|
|
# Modifying this file will now automatically clobber the buildbot machines \o/
|
|
#
|
|
|
|
# Are you updating CLOBBER because you think it's needed for your WebIDL
|
|
# changes to stick? As of bug 928195, this shouldn't be necessary! Please
|
|
# don't change CLOBBER for WebIDL changes any more.
|
|
|
|
Recent Android build system changes from bug 961339 and bug 946083 seem to be needs-clobbery.
|