[115429] trunk/base

Jeremy Huddleston Sequoia jeremyhu at macports.org
Wed Jan 1 16:52:17 PST 2014


On Jan 1, 2014, at 16:32, Ryan Schmidt <ryandesign at macports.org> wrote:
>> --- trunk/base/src/macports1.0/macports.tcl	2014-01-02 00:04:28 UTC (rev 115428)
>> +++ trunk/base/src/macports1.0/macports.tcl	2014-01-02 00:22:16 UTC (rev 115429)
>> @@ -956,6 +957,9 @@
>> 
>>     if {![info exists macports::macosx_deployment_target]} {
>> 
>>         set macports::macosx_deployment_target $macosx_version
>> 
>>     }
>> 
>> +    if {![info exists macports::macosx_sdk_version]} {
>> +        set macports::macosx_sdk_version $macosx_version
>> +    }
>> 
>> 
>> 
>>     if {![info exists macports::revupgrade_autorun]} {
>> 
>>         set macports::revupgrade_autorun yes
> 
> Some ports previously set macosx_deployment_target in order to change the sdk. Won’t this break those ports? I guess until MacPorts 2.3 is released those ports should check if [info exists macosx_sdk_version], if so set that, otherwise set macosx_deployment_target.

Yes, I was thinking that as well, so I grepped through dports before committing.  There were only a handful of references.  Most of them were using it for the deployment target, but there were a few that were relying on the undocumented "SDK" behavior.  Those will need to check [info exists macosx_sdk_version].

--Jeremy

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4145 bytes
Desc: not available
URL: <https://lists.macosforge.org/pipermail/macports-dev/attachments/20140101/f49b1799/attachment.p7s>


More information about the macports-dev mailing list