maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/clang-tools-extra/test/lit.site.cfg.py.in

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

25 lines
1.0 KiB
Python
Raw Normal View History

Replace hardcoded comment at 'lit.site.cfg.in' At the moment almost every lit.site.cfg.in contains two lines comment: ## Autogenerated by LLVM/Clang configuration. # Do not edit! The patch adds variable LIT_SITE_CFG_IN_HEADER, that is replaced from configure_lit_site_cfg with the note and some useful information. llvm-svn: 266518
2016-04-16 15:01:42 +08:00
@LIT_SITE_CFG_IN_HEADER@
Make lit.site.cfg Py3-compatible. Copied from r188041. llvm-svn: 198204
2013-12-30 14:18:08 +08:00
import sys
Reland "enable plugins for clang-tidy" This reverts commit ab3b89855c5318f0009e1f016ffe5b1483507fd0 but disables the new test if the user has disabled support for building it.
2022-02-02 01:05:20 +08:00
config.llvm_plugin_ext = "@LLVM_PLUGIN_EXT@"
Copy some of the testing infrastructure from the primary Clang repository into the new tools repo to preserve history. I'll subsequently be editting these down to work w/ the tooling test suites. llvm-svn: 161402
2012-08-07 15:09:14 +08:00
config.lit_tools_dir = "@LLVM_LIT_TOOLS_DIR@"
Add a root CMakeLists.txt and fix up all the test build stuff. With this we can build and test the remove-cstr-calls tool which should serve as a good example of how to add tools and their tests to the repository. llvm-svn: 161404
2012-08-07 16:33:04 +08:00
config.clang_tools_binary_dir = "@CLANG_TOOLS_BINARY_DIR@"
[clang-tools-extra] Reuse llvm_config.use_clang() to set up test environment This replaces a bunch of duplicate logic to set up environment variables and a few substitutions. It does a little more than we were doing previously: - searching for clang and setting up substitutions for it - setting up some substitutions for target triples, which are potentially useful but not actually used clangd has been happily using this for its tests for a while. Differential Revision: https://reviews.llvm.org/D121422
2022-03-11 07:29:10 +08:00
config.llvm_shlib_dir = "@SHLIBDIR@"
Revert "Temporarily revert "build: use `find_package(Python3)` if available"" This reverts commit 35edd704e0fda09e8e634515c0b451d4a8b6b914. Revert the revert and extend the patch further to account for the use of the `PYTHONINTERP_FOUND`.
2020-04-29 09:37:28 +08:00
config.python_executable = "@Python3_EXECUTABLE@"
[CMake] Rename TARGET_TRIPLE to LLVM_TARGET_TRIPLE This clarifies that this is an LLVM specific variable and avoids potential conflicts with other projects. Differential Revision: https://reviews.llvm.org/D119918
2021-12-02 17:04:46 +08:00
config.target_triple = "@LLVM_TARGET_TRIPLE@"
[clang-tools-extra] Reuse llvm_config.use_clang() to set up test environment This replaces a bunch of duplicate logic to set up environment variables and a few substitutions. It does a little more than we were doing previously: - searching for clang and setting up substitutions for it - setting up some substitutions for target triples, which are potentially useful but not actually used clangd has been happily using this for its tests for a while. Differential Revision: https://reviews.llvm.org/D121422
2022-03-11 07:29:10 +08:00
config.host_triple = "@LLVM_HOST_TRIPLE@"
Add an explicit toggle for the static analyzer in clang-tidy Instead of using CLANG_ENABLE_STATIC_ANALYZER for use of the static analyzer in both clang and clang-tidy, add a second toggle CLANG_TIDY_ENABLE_STATIC_ANALYZER. This allows enabling the static analyzer in clang-tidy while disabling it in clang. Differential Revison: https://reviews.llvm.org/D87118
2020-09-04 07:37:29 +08:00
config.clang_tidy_staticanalyzer = @CLANG_TIDY_ENABLE_STATIC_ANALYZER@
replace clang LLVM_ENABLE_PLUGINS -> CLANG_PLUGIN_SUPPORT in tests Ensure CLANG_PLUGIN_SUPPORT is compatible with llvm_add_library. Fixes an issue noted in D111100. Differential Revision: https://reviews.llvm.org/D119199
2022-02-08 07:46:33 +08:00
config.has_plugins = @CLANG_PLUGIN_SUPPORT@ & ~@LLVM_INSTALL_TOOLCHAIN_ONLY@
Copy some of the testing infrastructure from the primary Clang repository into the new tools repo to preserve history. I'll subsequently be editting these down to work w/ the tooling test suites. llvm-svn: 161402
2012-08-07 15:09:14 +08:00
# Support substitution of the tools and libs dirs with user parameters. This is
# used when we can't determine the tool dir at configuration time.
[lit] add lit_config.substitute to interpolate lit_config.params A version of this logic appears in ~every lit.site.cfg.in (28 copies total). This patch just removes two, but I'll update the rest of llvm-project next. Differential Revision: https://reviews.llvm.org/D121427
2022-03-11 07:58:03 +08:00
config.llvm_tools_dir = lit_config.substitute("@LLVM_TOOLS_DIR@")
config.llvm_libs_dir = lit_config.substitute("@LLVM_LIBS_DIR@")
[cmake] Provide CURRENT_TOOLS_DIR centrally, replacing CLANG_TOOLS_DIR CLANG_TOOLS_DIR holds the the current bin/ directory, maybe with a %(build_mode) placeholder. It is used to add the just-built binaries to $PATH for lit tests. In most cases it equals LLVM_TOOLS_DIR, which is used for the same purpose. But for a standalone build of clang, CLANG_TOOLS_DIR points at the build tree and LLVM_TOOLS_DIR points at the provided LLVM binaries. Currently CLANG_TOOLS_DIR is set in clang/test/, clang-tools-extra/test/, and other things always built with clang. This is a few cryptic lines of CMake in each place. Meanwhile LLVM_TOOLS_DIR is provided by configure_site_lit_cfg(). This patch moves CLANG_TOOLS_DIR to configure_site_lit_cfg() and renames it: - there's nothing clang-specific about the value - it will also replace LLD_TOOLS_DIR, LLDB_TOOLS_DIR etc (not in this patch) It also defines CURRENT_LIBS_DIR. While I removed the last usage of CLANG_LIBS_DIR in e4cab4e24d1, there are LLD_LIBS_DIR usages etc that may be live, and I'd like to mechanically update them in a followup patch. Differential Revision: https://reviews.llvm.org/D121763
2022-03-16 10:13:44 +08:00
config.clang_tools_dir = lit_config.substitute("@CURRENT_TOOLS_DIR@")
Copy some of the testing infrastructure from the primary Clang repository into the new tools repo to preserve history. I'll subsequently be editting these down to work w/ the tooling test suites. llvm-svn: 161402
2012-08-07 15:09:14 +08:00
Import lit.llvm after rL341130 llvm-svn: 341152
2018-08-31 08:26:46 +08:00
import lit.llvm
Remove LIT_SITE_CFG_IN_FOOTER, clang-tools-extra It's always replaced with the same (short) static string, so just put that there directly. No intended behavior change. https://reviews.llvm.org/D51357 llvm-svn: 341130
2018-08-31 06:10:13 +08:00
lit.llvm.initialize(lit_config, config)
Reland "[lit] Adding config initialization to lit tests in clang-tools-extra" Adding the config initialization to clang-tools-extra so that tests that use REQUIRES, UNSUPPORTED, and XFAIL based on platform or target triple work properly. llvm-svn: 328131
2018-03-22 02:50:26 +08:00
Copy some of the testing infrastructure from the primary Clang repository into the new tools repo to preserve history. I'll subsequently be editting these down to work w/ the tooling test suites. llvm-svn: 161402
2012-08-07 15:09:14 +08:00
# Let the main config do the real work.
Add .py extension to clang-tools-extra lit cfg files Follow-up to r313892, which did this for clang and llvm. Differential Revision: https://reviews.llvm.org/D59953 llvm-svn: 357231
2019-03-29 10:46:31 +08:00
lit_config.load_config(config, "@CLANG_TOOLS_SOURCE_DIR@/test/lit.cfg.py")