CLOBBER
author Chris Manchester <cmanchester@mozilla.com>
Fri, 10 Feb 2017 08:34:08 -0800
changeset 352238 994b97c9de3741e5bea37a8baf1573ded2323336
parent 351049 916a4ee676a33355fc717f15ecb80815ba95051e
child 352750 819a666afddc804b6099ee1b3cff3a0fdf35ec15
permissions -rw-r--r--
Bug 1337986 - Dump symbols during the compile tier. r=ted This commit moves symbol dumping to the compile tier, to be run via "syms" targets. Tracking files are used for the sake of incremental builds, because dump_syms may genearate multiple outputs whose paths are not known ahead of time. Minimal changes to symbolstore.py are made here. More extensive simplifications will be made in a future commit on the basis of symbolstore.py handling one file at a time. MozReview-Commit-ID: 3mOP8A6Y7iM

# 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.

Bug 1351074 - required because bug 1352982 means removing a .jsm requires a clobber