On Jun 26, 2009, at 11:14 AM, Jeremy Huddleston wrote:
On Jun 26, 2009, at 11:05, Toby Peterson wrote:
On Jun 26, 2009, at 9:43 AM, Jeremy Huddleston wrote:
With the universal_sysroot and universal_target now gone from
trunk, how is one expected to set macosx_deployment_target? I
thought that setting macosx_deployment_target in macports.conf
would do it, but nope...
Basically, you aren't. MacPorts doesn't support building for other
Mac OS X releases... although it is true that universal_target was
being abused to attempt it.
https://trac.macports.org/ticket/19875
Ok, so then why are we keeping macosx_deployment_target around at
all? Is there a reason to have this variable clutter up the
namespace if it's redundant with macosx_version?
You can set it for an individual port, which could (at least in
theory) be useful if for some reason the current deployment target
doesn't work.
- Toby
_______________________________________________
macports-dev mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
