• Home
  • Raw
  • Download

Lines Matching refs:libc

138   "Build libc++abi with an externalized threading API.
141 "Build libc++abi with an externalized threading library.
143 option(LIBCXXABI_BUILD_32_BITS "Build 32 bit libc++abi." ${LLVM_BUILD_32_BITS})
144 option(LIBCXXABI_INCLUDE_TESTS "Generate build targets for the libc++abi unit tests." ${LLVM_INCLUD…
148 set(LIBCXXABI_LIBCXX_LIBRARY_PATH "" CACHE PATH "The path to libc++ library.")
151 # the libc++abi that is being built. There are two problems with testing a
152 # static libc++abi. In the case of a standalone build, the tests will link the
153 # system's libc++, which might not have been built against our libc++abi. In the
154 # case of an in tree build, libc++ will prefer a dynamic libc++abi from the
155 # system over a static libc++abi from the output directory.
156 option(LIBCXXABI_ENABLE_SHARED "Build libc++abi as a shared library." ON)
157 option(LIBCXXABI_ENABLE_STATIC "Build libc++abi as a static library." ON)
160 message(FATAL_ERROR "libc++abi must be built as either a shared or static library.")
188 "Specify path to libc++ includes." FORCE)
205 "Specify path to libc++ source." FORCE)
230 "The path to libc++ library.")
285 string(REPLACE "-stdlib=libc++" "" CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS}")
495 # We can't reasonably test the system C++ library with a static libc++abi.
496 # We either need to be able to replace libc++abi at run time (with a shared
497 # libc++abi), or we need to be able to replace the C++ runtime (with a non-
499 message(WARNING "The libc++abi tests aren't valid when libc++abi is built "
502 "library, build libc++abi at the same time as you build "
503 "libc++, or do without testing. No check target will be "