diff options
author | Peter Collingbourne <peter@pcc.me.uk> | 2013-10-06 22:13:19 +0000 |
---|---|---|
committer | Peter Collingbourne <peter@pcc.me.uk> | 2013-10-06 22:13:19 +0000 |
commit | d0d308f54baaa977292b6ea586a9577aa6e2a8e4 (patch) | |
tree | b984a9cf942a8e3c16a7c35e89f0118f5b95d700 /www/index.html | |
parent | 40455c65da679c5789c14b2081417c432cd1173c (diff) | |
download | external_libcxx-d0d308f54baaa977292b6ea586a9577aa6e2a8e4.tar.gz external_libcxx-d0d308f54baaa977292b6ea586a9577aa6e2a8e4.tar.bz2 external_libcxx-d0d308f54baaa977292b6ea586a9577aa6e2a8e4.zip |
Make it possible to link against libstdc++ as well as libsupc++ with CMake.
Linking against libstdc++, rather than libsupc++, is probably better
for people who need to link against clients of libstdc++. Because
libsupc++ is provided only as a static library, its globals are not
shared between the static library and the copy linked into libstdc++.
This has been found to cause at least one test failure.
This also removes a number of symbols which were multiply defined
between libstdc++ and libc++, only when linking with libstdc++.
Differential Revision: http://llvm-reviews.chandlerc.com/D1825
git-svn-id: https://llvm.org/svn/llvm-project/libcxx/trunk@192075 91177308-0d34-0410-b5e6-96231b3b80d8
Diffstat (limited to 'www/index.html')
-rw-r--r-- | www/index.html | 9 |
1 files changed, 8 insertions, 1 deletions
diff --git a/www/index.html b/www/index.html index 71d30b8e3..02470ea9a 100644 --- a/www/index.html +++ b/www/index.html @@ -248,11 +248,18 @@ End of search list. We can now run CMake: <ul> <li><code>CC=clang CXX=clang++ cmake -G "Unix Makefiles" - -DLIBCXX_CXX_ABI=libsupc++ + -DLIBCXX_CXX_ABI=libstdc++ -DLIBCXX_LIBSUPCXX_INCLUDE_PATHS="/usr/include/c++/4.7/;/usr/include/c++/4.7/x86_64-linux-gnu/" -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=/usr <libc++-source-dir></code></li> + <li>You can also substitute <code>-DLIBCXX_CXX_ABI=libsupc++</code> + above, which will cause the library to be linked to libsupc++ instead + of libstdc++, but this is only recommended if you know that you will + never need to link against libstdc++ in the same executable as libc++. + GCC ships libsupc++ separately but only as a static library. If a + program also needs to link against libstdc++, it will provide its + own copy of libsupc++ and this can lead to subtle problems. <li><code>make</code></li> <li><code>sudo make install</code></li> </ul> |