[cfe-dev] Using C++11 in clang-tools-extra Round 2

[Nico Weber]

On Mon, Jan 7, 2013 at 10:55 AM, Vane, Edwin <edwin.vane at intel.com> wrote:
> Near the end of November I first posed the question of using C++11 features in the clang-tools-extra repo. At the time I let the subject drop because of the problem identified of mixing standard libraries C++03 with C++11 between the llvm/clang builds and tools-extra. I'd like to look at this issue again.
>
> What if we decide to make use of C++11 in tools-extra and make a C++11-enabled llvm/clang build be a requirement? As far as the build goes, we can support this by removing clang-tools-extra from the check-all target if C++11 is not enabled. I'm not sure how easy this is to detect but perhaps we can introduce a cmake/configure option to make 'detection' easier.
>
> Should we make all tools in tools-extra C++11 enabled or have the tools 'opt-in'? I'd like to see cpp11-migrate use C++11 considering its purpose but clang-format sees a lot of work these days too and I'm not sure if that tool wants to be C++11-enabled too?

C++11 library support on OS X requires libc++, which in turn means
that binaries won't run on OS X versions earlier than 10.7. Then
again, newer Xcodes don't support 10.6 any more, so it's probably not
a big deal. Just wanted to point this out.

Likewise, libstdc++ doesn't build with -std=libc++ on linux either
(with libstdc++ 4.4, 4.6, 4.7). How available is libc++ on linux
systems? Do most distros offer a package for it?

Nico

>
> --
> Edwin Vane
>   Software Developer
>   Intel of Canada, Inc.
>
>
> _______________________________________________
> cfe-dev mailing list
> cfe-dev at cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev