config/autoconf.mk.in
author Mike Hommey <mh+mozilla@glandium.org>
Sat, 04 Oct 2014 10:34:35 +0900
changeset 232019 0ca2335fa5a1c5ae7f86e193523c64fa504b411a
parent 185345 562a915cea9cfc51fdfbaaae02ce4b5c501aa488
permissions -rw-r--r--
Bug 1077228 - Include the right autoconf.mk in GLOBAL_DEPS. r=mshal 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.

ifndef INCLUDED_AUTOCONF_MK
INCLUDED_AUTOCONF_MK = autoconf.mk
include $(DEPTH)/config/emptyvars.mk
@ALLSUBSTS@
include $(topsrcdir)/config/baseconfig.mk
endif