standard way to require c++11?
Lawrence Velázquez
larryv at macports.org
Thu Mar 19 11:06:21 PDT 2015
On Mar 19, 2015, at 1:56 PM, Michael Dickens <michaelld at macports.org> wrote:
> On Thu, Mar 19, 2015, at 01:54 PM, René J.V. Bertin wrote:
>> On Thursday March 19 2015 17:01:02 Chris Jones wrote:
>>
>>> Using gcc is a bad idea, this can lead to C++ runtime issues.
>>
>> On newer OS X versions where libc++ is the default (or only) C++ runtime.
>
> Exactly. If we key off of {${configure.cxx_stdlib} eq "libstdc++"}, then
> I think this can be made to work; er, mostly.
I believe this is only safe if you're absolutely sure that all the C++ objects your code uses or links with uses MacPorts' libstdc++ / libsupc++.
vq
More information about the macports-dev
mailing list