Getting the entire configure.cflags variable
jmr at macports.org
Sat Oct 4 01:47:21 PDT 2014
On 2014-10-4 11:09 , Ryan Schmidt wrote:
> On Oct 3, 2014, at 4:47 PM, Joshua Root wrote:
>> On 2014-10-4 07:04 , Ryan Schmidt wrote:
>>> "-arch" flags may or may not be doable. Joshua previously thought this was not fixable.
>> Depends what you mean by "this" and "fixable". Certainly it's impossible
>> for any variable that can be read at any point to always reflect the
>> existence of a variant that may not have been defined yet.
> Right, precisely that is the difficult bit. But what about this: we already have the variable "universal_variant". Ports can set "universal_variant no" to disable the standard universal variant, or set "universal_variant yes" to have it added. We could trace that variable to change the -arch flags in the various *flags variables.
That doesn't really buy us much, does it? The flags still wouldn't
necessarily contain their final values before universal_variant is set.
Getting back to the original question of the thread, there would be no
problem providing a way to see what it looks like the eventual CFLAGS
would contain, given the information that is currently known. What we
can't do is know how the input variables are going to change later in
More information about the macports-dev