On Sep 11, 2013, at 8:17, William Gallafent <will...@gallaf.net> wrote:
> On 11 September 2013 16:07, Jakub Sochor <ja...@sochor.me> wrote: >> So I would like to compile these packages with libc++ support. And probably >> it will be required to build with this support also their dependences. > > Apologies for the “me too”, but me too :) > > As Lawrence has said, there doesn't appear to be a standard way to do > this yet in macports. There is a way to do it in trunk/base as of a couple weeks ago. Please see the long thread on macports-dev about this (which changed subject multiple times: "RFC: PATCH: cxx_runtime option for macports.conf" or "Host Versus MacPorts lib[std]c++" or "Fortran Recipe"): cxx_stdlib libc++ buildfromsource always It is *not* for most users, so YMMV, don't report bugs without a patch to fix them, etc. Make sure you start from a fresh install. > I would suggest that the sensible way to achieve > it is to add a variant (probably called “c++11”) to packages which use > C++ That would be a maintainance NIGHTMARE. For one thing, C++11 doesn't mean libc++. For another, there are way more C++ ports out there, and this would have to be done at once. For another, we'd need to enforce variants (which is rather messy and not well supported in MacPorts) > , and to have that variant add the standard compiler and linker > flags to achieve the result you need! This doesn't help you > immediately of course, but it would be good to have a discussion here > (or in fact perhaps better on macports-dev, in fact) There was ... a few weeks ago ... > in order to start > getting this stuff in place (I'm sure that you and I are not the only > ones who will need this in the future!) Please give the existing support a try, fix bugs you find, etc. --Jeremy
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
