Building the LibC++ libraries

Martin_J_O_Riordan1 · February 1, 2016, 4:17pm

We currently build the LibC++ libraries with an alternative build system, mainly because historically it was not possible to build the library for a cross-compiler. That of course is getting better with the wholesale move over to CMake.

At the moment we build the library with ‘-std=c++11’. This seems to produce a library that is valid for linking with programs compiled for C++98 and C++11, and very few people seem to be compiling their code with C++14. We have no had reports of problems.

But should I really be building 3 versions of the library, one each for C++98, 11 and 14? Or will a C++14 built library be link compatible for all the earlier dialects?

Thanks,

MartinO

Dan_Albert · February 1, 2016, 5:46pm

Building one C++14 library is sufficient. It’s just the headers that need to be compatible with old standard versions, and Marshall and Eric are careful to keep them that way.

I’m pretty sure you couldn’t build the library as C++98 even if you wanted to.

Martin_J_O_Riordan1 · February 1, 2016, 8:13pm

Thanks Dan, this is good news J

MartinO

Topic		Replies	Views
libc++ C++14 compatibility Clang Frontend	2	63	June 21, 2016
[PATCH] Added support to libc++ for GCC 4.3, GCC 4.5, and most recent head of Clang. Clang Frontend	5	119	August 6, 2010
[libcxxabi] Would there be any interest / acceptance of a CMake build for libc++abi? Clang Frontend	0	75	August 5, 2012
Compilation of libc++ Clang Frontend	1	74	January 1, 2011
libc++ in Windows Clang Frontend	16	132	October 12, 2013

Building the LibC++ libraries

Related Topics