gecko-dev/config/autoconf.mk.in

ifndef INCLUDED_AUTOCONF_MK
INCLUDED_AUTOCONF_MK = autoconf.mk
include $(DEPTH)/config/emptyvars.mk
@ALLSUBSTS@
include $(topsrcdir)/config/baseconfig.mk
endif
Bug 912293 - Add a generic header and footer to generated Makefiles. r=gps 2013-09-05 04:01:45 +04:00			`ifndef INCLUDED_AUTOCONF_MK`
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. 2014-10-04 05:34:35 +04:00			`INCLUDED_AUTOCONF_MK = autoconf.mk`
Bug 861453 - Restore empty substs after bug 857557, but put them in a separate file, unlisted as a dependency for everything. r=gps 2013-04-16 10:23:18 +04:00			`include $(DEPTH)/config/emptyvars.mk`
Bug 742795 - Autogenerate autoconf.mk. r=ted 2012-08-06 17:19:50 +04:00			`@ALLSUBSTS@`
Bug 763987 - Normalize autoconf.mk.in. r=ted 2012-06-20 11:00:48 +04:00			`include $(topsrcdir)/config/baseconfig.mk`
Bug 912293 - Add a generic header and footer to generated Makefiles. r=gps 2013-09-05 04:01:45 +04:00			`endif`