On Jan 1, 2014, at 18:22, [email protected] wrote:
> Revision
> 115429
> Author
> [email protected]
> Date
> 2014-01-01 16:22:16 -0800 (Wed, 01 Jan 2014)
> Log Message
>
> Turn SDK version and deployment target into separate options
Thanks; I was thinking about this recently. But:
> --- 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.
_______________________________________________
macports-dev mailing list
[email protected]
https://lists.macosforge.org/mailman/listinfo/macports-dev
