a48f018bb7
Now that all jobs have moved over to the new style of Lit configuration, we can remove all traces of the legacy testing configuration system. This includes: - Cache settings that are not honored or useful anymore - Several CMake options that were only useful in the context of the legacy Lit configuration system - A bunch of Python support code that is not used anymore - The legacy lit.cfg.in files themselves Differential Revision: https://reviews.llvm.org/D134650 |
||
|---|---|---|
| .. | ||
| AArch64.cmake | ||
| AIX.cmake | ||
| Apple.cmake | ||
| Armv7Arm.cmake | ||
| Armv7Thumb-noexceptions.cmake | ||
| Armv8Arm.cmake | ||
| Armv8Thumb-noexceptions.cmake | ||
| FreeBSD.cmake | ||
| Generic-abi-unstable.cmake | ||
| Generic-asan.cmake | ||
| Generic-assertions.cmake | ||
| Generic-cxx2b.cmake | ||
| Generic-cxx03.cmake | ||
| Generic-cxx11.cmake | ||
| Generic-cxx14.cmake | ||
| Generic-cxx17.cmake | ||
| Generic-cxx20.cmake | ||
| Generic-debug-mode.cmake | ||
| Generic-merged.cmake | ||
| Generic-modules.cmake | ||
| Generic-msan.cmake | ||
| Generic-no-experimental.cmake | ||
| Generic-no-filesystem.cmake | ||
| Generic-no-localization.cmake | ||
| Generic-no-random_device.cmake | ||
| Generic-no-threads.cmake | ||
| Generic-no-transitive-includes.cmake | ||
| Generic-no-unicode.cmake | ||
| Generic-no-wide-characters.cmake | ||
| Generic-noexceptions.cmake | ||
| Generic-static.cmake | ||
| Generic-tsan.cmake | ||
| Generic-ubsan.cmake | ||
| MinGW.cmake | ||
| README.md | ||
README.md
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.