kdevelop 4.7 and beyond (was: clang++-mp-3.4 doesn't find initializer_list on OS X 10.6)

[Lawrence Velázquez]

On Sep 6, 2014, at 6:51 AM, Mojca Miklavec <mojca.miklavec.lists at gmail.com> wrote:

> I already argued that we really need a libc++-based buildbot for 10.6-10.8.
> 
> From what I understood all we need is a fix in binary package
> signature + time and resources to set up the buildbots. Once the
> buildbots run, people can start testing and switching to libc++. Once
> we get to a satisfactory support, we can recommend everyone to switch
> and retire the libstdc++-based buildbots if needed.
> 
> Switching from libstdc++ to libc++ would be equal to switching from
> 10.x to 10.(x+1). (Nice to automate one day, but people should switch
> manually for now and reinstall everything from scratch.)
> 
> The libc++-based MacPorts works well on < 10.9 already for most
> packages. Supporting libstdc++ is getting increasingly painful with
> more and more software depending on C++11.

What happens if MacPorts-built software wants to link to system software that doesn't use our libc++? Does the libc++ port link to the system libc++abi?

vq