Le vendredi 19 juin 2015 17:24:29 UTC+2, Ted Mielczarek a écrit :
> On Fri, Jun 19, 2015, at 10:11 AM, Alex wrote:
> > So as a test case I've got a Makefile referenced in the moz.build file
> > that sets CFLAGS and if I change the Makefile, the build systems detects
> > it 'Build configuration changed. Regenerating backend.' Problem is it
> > doesn't actually set the CFLAGS. 
> > 
> > So for example in gfx\qcms\moz.build I've added the top of the file:
> > CONFIGURE_SUBST_FILES += ['Makefile']
> 
> CONFIGURE_SUBST_FILES are *not* what you want for a Makefile.in that
> works alongside a moz.build as part of the normal build. That's for
> special-case stuff like "Makefiles that only implement special build
> targets" or "random files that want configure substitution". You just
> want to put a Makefile.in next to moz.build and it will be converted to
> a Makefile as part of moz.build processing.
> 
> > #Hide warnings in this directory
> > CFLAGS = -w 
> > 
> > The flags don't set and the warnings still show? I know moz.build has a
> > CFLAG option, this is just a test case if I ever need to add something
> > that moz.build doesn't yet.
> 
> Any individual make variable may or may not work. "It's complicated."
> There are things that get set from configure in autoconf.mk, there are
> things that get overridden in config.mk and rules.mk. Basically: YMMV.
> If there's a way to do it in moz.build just use that.
> 
> -Ted

Le vendredi 19 juin 2015 17:24:29 UTC+2, Ted Mielczarek a écrit :
> On Fri, Jun 19, 2015, at 10:11 AM, Alex wrote:
> > So as a test case I've got a Makefile referenced in the moz.build file
> > that sets CFLAGS and if I change the Makefile, the build systems detects
> > it 'Build configuration changed. Regenerating backend.' Problem is it
> > doesn't actually set the CFLAGS. 
> > 
> > So for example in gfx\qcms\moz.build I've added the top of the file:
> > CONFIGURE_SUBST_FILES += ['Makefile']
> 
> CONFIGURE_SUBST_FILES are *not* what you want for a Makefile.in that
> works alongside a moz.build as part of the normal build. That's for
> special-case stuff like "Makefiles that only implement special build
> targets" or "random files that want configure substitution". You just
> want to put a Makefile.in next to moz.build and it will be converted to
> a Makefile as part of moz.build processing.
> 
> > #Hide warnings in this directory
> > CFLAGS = -w 
> > 
> > The flags don't set and the warnings still show? I know moz.build has a
> > CFLAG option, this is just a test case if I ever need to add something
> > that moz.build doesn't yet.
> 
> Any individual make variable may or may not work. "It's complicated."
> There are things that get set from configure in autoconf.mk, there are
> things that get overridden in config.mk and rules.mk. Basically: YMMV.
> If there's a way to do it in moz.build just use that.
> 
> -Ted



Le vendredi 19 juin 2015 17:24:29 UTC+2, Ted Mielczarek a écrit :
> On Fri, Jun 19, 2015, at 10:11 AM, Alex wrote:
> > So as a test case I've got a Makefile referenced in the moz.build file
> > that sets CFLAGS and if I change the Makefile, the build systems detects
> > it 'Build configuration changed. Regenerating backend.' Problem is it
> > doesn't actually set the CFLAGS. 
> > 
> > So for example in gfx\qcms\moz.build I've added the top of the file:
> > CONFIGURE_SUBST_FILES += ['Makefile']
> 
> CONFIGURE_SUBST_FILES are *not* what you want for a Makefile.in that
> works alongside a moz.build as part of the normal build. That's for
> special-case stuff like "Makefiles that only implement special build
> targets" or "random files that want configure substitution". You just
> want to put a Makefile.in next to moz.build and it will be converted to
> a Makefile as part of moz.build processing.
> 
> > #Hide warnings in this directory
> > CFLAGS = -w 
> > 
> > The flags don't set and the warnings still show? I know moz.build has a
> > CFLAG option, this is just a test case if I ever need to add something
> > that moz.build doesn't yet.
> 
> Any individual make variable may or may not work. "It's complicated."
> There are things that get set from configure in autoconf.mk, there are
> things that get overridden in config.mk and rules.mk. Basically: YMMV.
> If there's a way to do it in moz.build just use that.
> 
> -Ted

_______________________________________________
dev-builds mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-builds

Reply via email to