All the more reason for "mach" to be the exclusive place to put all these smarts.
The only things I really want anyway are: mk_add_options MOZ_OBJDIR=obj-bug ac_add_options --enable-debug='-g3 -O0 -fno-inline' ac_add_options --disable-optimize On Tue, Dec 20, 2016 at 10:41 PM, J. Ryan Stinnett <jry...@gmail.com> wrote: > On Wed, Dec 21, 2016 at 12:23 AM, Jim Blandy <jbla...@mozilla.com> wrote: > > I had a .mozconfig file that included the line: > > > > . "$topsrcdir/build/mozconfig.common" > > My understanding is that we're generally not supposed to include the > in-tree mozconfigs in our local builds, since they are free to make > various automation-only assumptions, which seems to be what happened > here. It's tempting to do it anyway though, for some abstract feeling > that the build will more closely resemble an official one. (I used to > do something like this as well!) > > I believe many people have fallen into this trap over the years, most > likely because of MDN pages[1] that appeared to suggest using > automation mozconfigs directly (there's at least a warning on the page > now). > > [1]: https://developer.mozilla.org/en-US/docs/Mozilla/Developer_ > guide/Build_Instructions/Configuring_Build_Options# > Example_.mozconfig_Files > > - Ryan > _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
