Lines Matching refs: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
163 directory as the tested libc++ DLL.
165 (Building a libc++ that depends on libstdc++ isn't necessarily a config one
168 .. _`libc++abi`: http://libcxxabi.llvm.org/
190 The C++ compiler to use when building and testing libc++.
195 libc++ specific options
202 Toggle the installation of the library portion of libc++.
208 Toggle the installation of the libc++ headers.
214 Build libc++ with assertions enabled.
220 Build libc++ as a 32 bit library. Also see `LLVM_BUILD_32_BITS`.
226 Build libc++ as a shared library. Either `LIBCXX_ENABLE_SHARED` or
233 Build libc++ as a static library. Either `LIBCXX_ENABLE_SHARED` or
245 Do not export any symbols from the static libc++ library.
246 This is useful when the static libc++ library is being linked into shared
248 C++ library. We want to avoid exporting any libc++ symbols in that case.
259 libc++experimental Specific Options
266 Build and test libc++experimental.a.
272 Install libc++experimental.a alongside libc++.
284 Select the ABI library to build libc++ against.
292 Provide the path to the ABI library that libc++ should link against.
298 If this option is enabled, libc++ will try and link the selected ABI library
306 This option generate and installs a linker script as ``libc++.so`` which
314 libc++abi is the C++ ABI library used.
317 libc++ Feature Options
324 Build libc++ with exception support.
330 Build libc++ with run time type information.
336 Build the libc++ tests.
342 Build the libc++ benchmark tests and the Google Benchmark library needed
349 A semicolon list of arguments to pass when running the libc++ benchmarks using the
358 **Values**:: ``libc++``, ``libstdc++``
360 Build the libc++ benchmark tests and Google Benchmark library against the
362 compare libc++ to libstdc++ by building the benchmark tests against both
380 libc++ ABI Feature Options
383 The following options allow building libc++ for a different ABI version.
389 Defines the target ABI version of libc++.
395 Build the "unstable" ABI version of libc++. Includes all ABI changing features
403 custom versions of libc++ with unique symbol names in order to prevent conflicts or ODR issues
404 with other libc++ versions.
408 conflicts with other names defined by libc++, both now and in the future. In particular, inline
409 … namespaces of the form ``__[0-9]+`` are strictly reserved by libc++ and may not be used by users.
410 Doing otherwise could cause conflicts and hinder libc++ ABI evolution.
487 <libc++-source-dir>
493 never need to link against libstdc++ in the same executable as libc++.
503 You can now run clang with -stdlib=libc++.
524 <libc++-source-directory>
528 Unfortunately you can't simply run clang with "-stdlib=libc++" at this point, as
529 clang is set up to link for libc++ linked to libsupc++. To get around this
534 $ clang++ -stdlib=libc++ helloworld.cpp \
542 $ clang++ -stdlib=libc++ helloworld.cpp -lcxxrt
555 Normally you must link libc++ against a ABI shared library that the
556 linker can find. If you want to build and test libc++ against an ABI
560 An example build using libc++abi would look like:
565 -DLIBCXX_CXX_ABI=libc++abi \
571 When testing libc++ LIT will automatically link against the proper ABI