Branko Čibej wrote on Fri, Dec 21, 2012 at 19:40:03 +0100: > On 21.12.2012 19:17, Philip Martin wrote: > > Branko Čibej <br...@wandisco.com> writes: > > > >> On 21.12.2012 18:30, Philip Martin wrote: > >>> Branko Čibej <br...@wandisco.com> writes: > >>> > >>>> Does "make EXTRA_CFLAGS=..." not give you exactly that? > >>> I want to set the flags at configure. > >> Sure, I understand that. But in order to do that, we'd have to introduce > >> another variable besides C(XX)FLAGS, because those override whatever > >> AC_PROG_CC would attempt to set, and always get used for bindings. > >> > >> Internally, configure already uses C(XX)USERFLAGS that could be > >> repurposed for that kind of use, or even C(XX)MAINTAINERFLAGS, which > >> have the right properties in that they're not used to compile swig > >> wrappers and such. > >> > >> Would that satisfy your requirements? > > I suppose I want to be able to specify an initial value for > > CMAINTAINERFLAGS: > > > > configure CMAINTAINERFLAGS=--something-special > > > > Then our code builds with --something-special, in addition to whatever > > configure chooses to add, while the generated code builds without my > > extra flag. > > > > I wouldn't hold up your branch for this, trunk doesn't support it > > either. > > Sure. But this exact use is amazingly easy to support, given the > infrastructure already present on the branch. So I'll just make it work, > even without --maintainer-mode.
Can someone spell out the conclusion please? How do I add something to CFLAGS at configure time --- by setting CMAINTAINERFLAGS? What if I set CFLAGS, would that append or replace to whatever configure things the flags should be? Thanks, Daniel
