[libc++][CMake] Add CMake caches for commonly supported configurations

This commit adds CMake caches for the various configurations of libc++
that are tested by our build bots.

Differential Revision: https://reviews.llvm.org/D81293
This commit is contained in:
Louis Dionne 2019-04-16 17:12:54 -04:00
parent ce5fecb7d0
commit d9dec697cb
13 changed files with 29 additions and 0 deletions

View File

@ -0,0 +1 @@
set(LLVM_BUILD_32_BITS ON CACHE BOOL "")

View File

@ -0,0 +1 @@
set(LLVM_USE_SANITIZER "Address" CACHE STRING "")

View File

@ -0,0 +1 @@
set(LLVM_LIT_ARGS "--param std=c++03" CACHE STRING "")

View File

@ -0,0 +1 @@
set(LLVM_LIT_ARGS "--param std=c++11" CACHE STRING "")

View File

@ -0,0 +1 @@
set(LLVM_LIT_ARGS "--param std=c++14" CACHE STRING "")

View File

@ -0,0 +1 @@
set(LLVM_LIT_ARGS "--param std=c++17" CACHE STRING "")

View File

@ -0,0 +1 @@
set(LLVM_LIT_ARGS "--param std=c++2a" CACHE STRING "")

View File

@ -0,0 +1 @@
set(LLVM_USE_SANITIZER "MemoryWithOrigins" CACHE STRING "")

View File

@ -0,0 +1,2 @@
set(LIBCXX_ENABLE_EXCEPTIONS OFF CACHE BOOL "")
set(LIBCXXABI_ENABLE_EXCEPTIONS OFF CACHE BOOL "")

View File

@ -0,0 +1,3 @@
set(LIBCXX_ENABLE_THREADS OFF CACHE BOOL "")
set(LIBCXXABI_ENABLE_THREADS OFF CACHE BOOL "")
set(LIBCXX_ENABLE_MONOTONIC_CLOCK OFF CACHE BOOL "")

View File

@ -0,0 +1 @@
set(LLVM_USE_SANITIZER "Thread" CACHE STRING "")

View File

@ -0,0 +1,2 @@
set(LLVM_USE_SANITIZER "Undefined" CACHE STRING "")
set(LIBCXX_ABI_UNSTABLE ON CACHE BOOL "")

View File

@ -0,0 +1,13 @@
# libc++ / libc++abi configuration caches
This directory contains CMake caches for the supported configurations of libc++.
Some of the configurations are specific to a vendor, others are generic and not
tied to any vendor.
While we won't explicitly work to break configurations not listed here, any
configuration not listed here is not explicitly supported. If you use or ship
libc++ under a configuration not listed here, you should work with the libc++
maintainers to make it into a supported configuration and add it here.
Similarly, adding any new configuration that's not already covered must be
discussed with the libc++ maintainers as it entails a maintenance burden.