Multiple MacPort prefixes

[Tres Finocchiaro]

On Wed, Dec 17, 2014 at 9:47 AM, Joshua Root <jmr at macports.org> wrote:
>
> Xcode 3.x is not the right version to use with Lion, 4.x is. 3.1 is for
> Leopard and 3.2 is for Snow Leopard. IIRC, 3.2.6 didn't even work right
> on Lion, so I wouldn't expect it to work on Mavericks.
>

Sorry, typo, 4.6.3 is the exact Lion SDK version that was installed.  My
mistake. :)


>
> The Apple-endorsed way to build for an older OS version has always been
> to use the latest Xcode and set MACOSX_DEPLOYMENT_TARGET to the oldest
> version you want to target.
>

Yes, this is the approach I am using.



> MacPorts doesn't officially support doing this, mainly because
> autoconf and similar systems consider it to be cross-compiling and need you
> to
> tell them about the target manually, instead of being able to detect
> the characteristics of the build machine automatically.


Gotcha.


> > Ideally, I'd like to have two MacPorts installs that I can build software
> > against... One for Mavericks and a second instance for Lion.
>
> You can certainly configure MacPorts to use a different prefix when
> building it from source.
>

 Ok, so this option is only available when building the MacPorts software
from source.  I'd rather not add more cruft.  I'll fire up a Lion VM for
this, thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.macosforge.org/pipermail/macports-users/attachments/20141217/de960dd3/attachment.html>