Getting the entire configure.cflags variable

Lawrence Velázquez larryv at
Thu Oct 2 14:29:50 PDT 2014

On Oct 2, 2014, at 5:13 PM, Ryan Schmidt <ryandesign at> wrote:

> On Oct 2, 2014, at 4:10 PM, Lawrence Velázquez wrote:
>> I suspect the idea is to prevent ports from clearing CFLAGS and such.
> I think it's more that in many cases -- arch flags for example, or which C++ stdlib flag to use -- MacPorts won't know what to put in the cflags until after the rest of the port has been processed. What if you append something to configure.cflags, then later turn on (or turn off) the universal variant? Then the wrong arch flags will be in configure.cflags. This is why (as I understand it) MacPorts doesn't put them in until the port has been completely evaluated.

For my part, when I implemented configure.cxx_stdlib, I was primarily thinking about preventing Portfiles from trashing the "-stdlib" argument. Augmenting configure.cxxflags seemed preferable to arcane Tcl sorcery.


More information about the macports-dev mailing list