On Jun 19, 2015, at 6:23 AM, René J.V. Bertin wrote:

> On Friday June 19 2015 06:02:53 Ryan Schmidt wrote:
> 
>> MacPorts always sets the MACOSX_DEPLOYMENT_TARGET environment variable, in 
>> every phase, to the value of the MacPorts Tcl variable 
>> macosx_deployment_target. The default value of macosx_deployment_target is 
>> the currently running OS X major version (like 10.8 or 10.10). It can be 
>> changed by the portfile author if needed for a particular port, or globally 
>> by the user in macports.conf. The latter is undocumented and unsupported but 
>> basically functional.
> 
> Aha! I don't have this variable in my macports.conf; has there been any 
> change to this policy in recent months? That would be about the only logical 
> explanation for that mysterious issue I'm seeing with the NSMetadata token (= 
> if my earlier build where the symbol was and still is found was done 
> targeting OS X <= 10.8).

You are correct, macosx_deployment_target is deliberately not listed in 
macports.conf, because it is unsupported.

_______________________________________________
macports-dev mailing list
[email protected]
https://lists.macosforge.org/mailman/listinfo/macports-dev

Reply via email to