Lines Matching full:libc
4 Building libc++
20 (optionally) install libc++ and libc++abi.
22 If your system already provides a libc++ installation it is important to be
24 ``CMAKE_INSTALL_PREFIX`` to select a safe place to install libc++.
27 * Replacing your systems libc++ installation could render the system non-functional.
28 * macOS will not boot without a valid copy of ``libc++.1.dylib`` in ``/usr/lib``.
43 For more information about configuring libc++ see :ref:`CMake Options`. You may
47 Shared libraries for libc++ and libc++ abi should now be present in
48 ``build/lib``. See :ref:`using an alternate libc++ installation <alternate
49 libcxx>` for information on how to use this libc++.
51 The instructions are for building libc++ on
52 FreeBSD, Linux, or Mac using `libc++abi`_ as the C++ ABI library.
55 It is possible to build libc++ standalone (i.e. without building other LLVM
123 .. _`libc++abi`: http://libcxxabi.llvm.org/
145 The C++ compiler to use when building and testing libc++.
150 libc++ specific options
157 Toggle the installation of the library portion of libc++.
163 Toggle the installation of the libc++ headers.
169 Build libc++ with assertions enabled.
175 Build libc++ as a 32 bit library. Also see `LLVM_BUILD_32_BITS`.
181 Build libc++ as a shared library. Either `LIBCXX_ENABLE_SHARED` or
188 Build libc++ as a static library. Either `LIBCXX_ENABLE_SHARED` or
200 Define libc++ destination prefix.
206 Do not export any symbols from the static libc++ library.
207 This is useful when the static libc++ library is being linked into shared
209 C++ library. We want to avoid exporting any libc++ symbols in that case.
220 libc++experimental Specific Options
227 Build and test libc++experimental.a.
233 Install libc++experimental.a alongside libc++.
245 Select the ABI library to build libc++ against.
253 Provide the path to the ABI library that libc++ should link against.
259 If this option is enabled, libc++ will try and link the selected ABI library
267 This option generate and installs a linker script as ``libc++.so`` which
275 libc++abi is the C++ ABI library used.
278 libc++ Feature Options
285 Build libc++ with exception support.
291 Build libc++ with run time type information.
297 Build the libc++ tests.
303 Build the libc++ benchmark tests and the Google Benchmark library needed
310 A semicolon list of arguments to pass when running the libc++ benchmarks using the
319 **Values**:: ``libc++``, ``libstdc++``
321 Build the libc++ benchmark tests and Google Benchmark library against the
323 compare libc++ to libstdc++ by building the benchmark tests against both
341 libc++ ABI Feature Options
344 The following options allow building libc++ for a different ABI version.
350 Defines the target ABI version of libc++.
356 Build the "unstable" ABI version of libc++. Includes all ABI changing features
364 custom versions of libc++ with unique symbol names in order to prevent conflicts or ODR issues
365 with other libc++ versions.
369 conflicts with other names defined by libc++, both now and in the future. In particular, inline
370 … namespaces of the form ``__[0-9]+`` are strictly reserved by libc++ and may not be used by users.
371 Doing otherwise could cause conflicts and hinder libc++ ABI evolution.
448 <libc++-source-dir>
454 never need to link against libstdc++ in the same executable as libc++.
464 You can now run clang with -stdlib=libc++.
485 <libc++-source-directory>
489 Unfortunately you can't simply run clang with "-stdlib=libc++" at this point, as
490 clang is set up to link for libc++ linked to libsupc++. To get around this
495 $ clang++ -stdlib=libc++ helloworld.cpp \
503 $ clang++ -stdlib=libc++ helloworld.cpp -lcxxrt
516 Normally you must link libc++ against a ABI shared library that the
517 linker can find. If you want to build and test libc++ against an ABI
521 An example build using libc++abi would look like:
526 -DLIBCXX_CXX_ABI=libc++abi \
532 When testing libc++ LIT will automatically link against the proper ABI