llvm-project/libcxxabi/test/lit.site.cfg.in

@AUTO_GEN_COMMENT@
config.cxx_under_test         = "@LIBCXXABI_COMPILER@"
config.libcxxabi_src_root     = "@LIBCXXABI_SOURCE_DIR@"
config.libcxxabi_library_root = "@LIBCXXABI_LIBRARY_DIR@"
config.python_executable      = "@PYTHON_EXECUTABLE@"
config.enable_shared          = @LIBCXXABI_ENABLE_SHARED@
config.libcxx_includes        = "@LIBCXXABI_LIBCXX_INCLUDES@"
config.llvm_unwinder          = @LIBCXXABI_USE_LLVM_UNWINDER@
config.enable_threads         = @LIBCXXABI_ENABLE_THREADS@
config.llvm_use_sanitizer     = "@LLVM_USE_SANITIZER@"

# Let the main config do the real work.
lit_config.load_config(config, "@LIBCXXABI_SOURCE_DIR@/test/lit.cfg")
Add lit configs for libcxxabi tests. This makes running libcxxabi tests on Linux _much_ easier. Adds a check-libcxxabi target to cmake. Also defaults to building a dynamic libc++abi. This is so that the default options still test the libc++abi that is being built. There are two problems with testing a static libc++abi. In the case of a standalone build, the tests will link the system's libc++, which might not have been built against our libc++abi. In the case of an in tree build, libc++ will prefer a dynamic libc++abi from the system over a static libc++abi from the output directory. llvm-svn: 212672 2014-07-10 10:20:11 +08:00			`@AUTO_GEN_COMMENT@`
[cmake/multilib] Teach libc++abi's CMake build to support multilib libdir suffixes like 'lib64' or 'lib32'. This support is currently very rhudimentary. We define a variable LIBCXXABI_LIBDIR_SUFFIX. In a standalone build of libc++abi this can be directly set as a cached variable to control the multilib suffix used. When building libc++abi within a larger LLVM build, it is hard wired to whatever LLVM libdir suffix has been selected. If this doesn't work for someone, just let me know. I'm happy to change it. Unfortunately, libc++abi's lit setup made this somewhat problematic to change. It was setting variables up in a way that caused the resulting build to not work with lit at all. To fix that, I've moved some variables around in the CMake build to more closely match where and how they are defined in the libc++ CMake build. This includes specifically defining a library root variable in the CMake build where the libdir suffix can be applied, and then using that rather than re-computing it from the object directory in the lit config. This is essentially new functionality for libc++abi so I don't expect it to have any impact for folks until they start setting these variables. However, I know libc++abi is built in a diverse set of environments so just let me know if this causes you any problems. llvm-svn: 224927 2014-12-29 20:22:04 +08:00			`config.cxx_under_test = "@LIBCXXABI_COMPILER@"`
			`config.libcxxabi_src_root = "@LIBCXXABI_SOURCE_DIR@"`
			`config.libcxxabi_library_root = "@LIBCXXABI_LIBRARY_DIR@"`
			`config.python_executable = "@PYTHON_EXECUTABLE@"`
			`config.enable_shared = @LIBCXXABI_ENABLE_SHARED@`
			`config.libcxx_includes = "@LIBCXXABI_LIBCXX_INCLUDES@"`
			`config.llvm_unwinder = @LIBCXXABI_USE_LLVM_UNWINDER@`
			`config.enable_threads = @LIBCXXABI_ENABLE_THREADS@`
			`config.llvm_use_sanitizer = "@LLVM_USE_SANITIZER@"`
Add lit configs for libcxxabi tests. This makes running libcxxabi tests on Linux _much_ easier. Adds a check-libcxxabi target to cmake. Also defaults to building a dynamic libc++abi. This is so that the default options still test the libc++abi that is being built. There are two problems with testing a static libc++abi. In the case of a standalone build, the tests will link the system's libc++, which might not have been built against our libc++abi. In the case of an in tree build, libc++ will prefer a dynamic libc++abi from the system over a static libc++abi from the output directory. llvm-svn: 212672 2014-07-10 10:20:11 +08:00
			`# Let the main config do the real work.`
			`lit_config.load_config(config, "@LIBCXXABI_SOURCE_DIR@/test/lit.cfg")`