On Tue, Apr 8, 2014 at 2:46 PM, Chris Jones wrote:
>
> Thats OK for a standalone build, but the whole point of having root in
> macports is to pick up various dependencies from Macports. This trick would
> then only work if the user built all of these dependencies against libc++ as
> well. SO unless MacPorts is planning on switch its 10.8 builds to by default
> use libc++, this doesn't help much with getting the port working on 10.8
One option could be
if 10.9 or later:
use dependencies from MacPorts
else:
use just the built-in libraries without any advanced
functionality or external libraries
which is still better than having a nonfunctional port ... of course
only if that works at all.
Mojca
_______________________________________________
macports-dev mailing list
[email protected]
https://lists.macosforge.org/mailman/listinfo/macports-dev
