Gregory Szorc wrote:
OK, so you run make, make.py, or mozmake to build the tree. Do you
ever perform partial tree builds? That is: |make -C dom| or |cd dom;
make|. If so, you may be impacted by a recent change to the build system.
If you attempt to perform a partial tree build directly with a make
implementation and the build configuration (moz.build files,
Makefile.in, test manifests, etc) is out of date, the build will error
fast, printing a message like:
/Users/gps/src/firefox/config/rules.mk:595: *** Build configuration
changed. Build with |mach build| or run |mach build-backend| to
regenerate build config. Stop.
That should be self-explanatory. If not, file a bug and we'll get the
error message updated.
If you are concerned about this change taking away a feature, I assure
you there are good reasons. The gory details are in bug 877308 [1]. I
won't attempt to explain them here because there is some serious build
system and make voodoo involved.
I don't build with mach because comm-central doesn't integrate very well
with it.
I also am used to triggering a build configuration change with mozmake
-C ${OBJDIR}/mozilla Makefile because comm-central's build system
historically failed to trigger it when one of its Makefiles changed.
Will this command continue to work?
--
Warning: May contain traces of nuts.
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
