Closed Bug 1077228 Opened 6 years ago Closed 6 years ago

Some changes to autoconf-js.mk don't trigger rebuilds

Categories

(Firefox Build System :: General, defect)

defect
Not set
normal

Tracking

(firefox32 affected, firefox33 affected, firefox34 affected, firefox35 affected, firefox-esr31 affected)

RESOLVED FIXED
mozilla35
Tracking Status
firefox32 --- affected
firefox33 --- affected
firefox34 --- affected
firefox35 --- affected
firefox-esr31 --- affected

People

(Reporter: glandium, Assigned: glandium)

References

Details

Attachments

(1 file)

No description provided.
Blocks: 969164
Ever since bug 969164, the js build system, when building gecko (not when
building standalone) uses a autoconf-js.mk file for its config.

One of the suboptimal ways we have to retrigger builds when the build
configuration changes (changes to e.g. configure.in can do that) is to
make most things depend on autoconf.mk. Which unfortunately doesn't
account for the fact the js/src subdirectory uses a different file.

In practice, this means that some classes of changes to the js build
system, not accompanied with toplevel build system changes may no
trigger the corresponding rebuilds in the js subtree on incremental
builds.
Attachment #8499287 - Flags: review?(mshal)
Attachment #8499287 - Flags: review?(mshal) → review+
https://hg.mozilla.org/mozilla-central/rev/0ca2335fa5a1
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla35
Product: Core → Firefox Build System
You need to log in before you can comment on or make changes to this bug.