summaryrefslogtreecommitdiffstats
path: root/llvm/utils/llvm-lit/llvm-lit.in
Commit message (Collapse)AuthorAgeFilesLines
* Revert r229224: Make the 'llvm-lit' utility defend against a system where ↵Chandler Carruth2015-02-141-1/+1
| | | | | | | | Python3 Apparantly python2.7 also doesn't work. Awesome. llvm-svn: 229245
* [lit] Make the 'llvm-lit' utility defend against a system where Python3Chandler Carruth2015-02-141-1/+1
| | | | | | | | | | | | | is the default. The lit.cfg files are not all valid Python3 and I've no idea if anyone is really prepared to update them. The easiest way I know of to ensure that this script uses Python 2 is to use 'python2.7' in the command. Mac and Linux are definitely fine with this and I think other platforms will be as well, but if anyone struggles with this set up and has better ideas, let me know. llvm-svn: 229244
* [testing]: lld generally lives in tools/, so fix llvm-lit.Tim Northover2014-07-071-1/+1
| | | | | | Otherwise we can't run individual tests directly ("llvm-lit /path/to/test") llvm-svn: 212461
* lit: Set a base directory for compiler-rt testsDuncan P. N. Exon Smith2014-03-311-0/+5
| | | | | | | | | Setting this parameter enables llvm-lit to run on source directories for compiler-rt test suites that implement magic in their lit.cfg. <rdar://problem/16458307> llvm-svn: 205262
* Add the lld root to llvm-lit, so llvm-lit can be usedJoey Gouly2014-01-141-0/+5
| | | | | | to run lld tests individually. llvm-svn: 199264
* [CMake] Generate ${BUILD_MODE}/llvm-lit for each ${CMAKE_CONFIGURATION_TYPES}.NAKAMURA Takumi2013-12-301-1/+1
| | | | | | | | | | | | llvm-lit can be invoked; $ Release/bin/llvm-lit instead of; $ bin/llvm-lit --param buid_mode=Release llvm-svn: 198206
* Add missing trailing comma in llvm-lit.inReid Kleckner2013-12-171-1/+1
| | | | | | | I was testing a stale bin/llvm-lit, which now lives at bin/llvm-lit.py on Windows. llvm-svn: 197446
* Add the lit site config for unittests to bin/llvm-litReid Kleckner2013-12-171-0/+2
| | | | | | | | | | This missing parameter was causing bin/llvm-lit to run the unittests from my primary build directory instead of my self-hosting build directory because llvm-config was on my PATH. This more closely matches what 'make check' will pass to lit.py. llvm-svn: 197444
* [CMake][Lit][unittests] Deprecate CMAKE_BUILD_TYPE in each build directory ↵NAKAMURA Takumi2013-01-271-2/+1
| | | | | | | | | | | | | | | | | | | | | | | | for unittests. For example, cur) unittests/ADT/Release/ADTTests new) unittests/ADT/ADTTests RUNTIME_BUILD_MODE can be substituted to CMAKE_CFG_INTDIR. With Make and Ninja, the tree is not built with multiple configurations. Then, including the build type in target directory doesn't make sense. See also "How can I build multiple modes without switching?" http://www.cmake.org/Wiki/CMake_FAQ CMAKE_CFG_INTDIR is set to "." With multiple-configuration-aware build system, like Visual Studio, each unittest is built on appropriate directory, for example, unittests/ADT/Release/ADTTests.exe CMAKE_CFG_INTDIR is set to build system's variable, like "$(Configuration)" or "$(OutDir)". Thus, "--param build_config" is also deprecated. llvm-svn: 173616
* [LIT] Add a clang_tools_extra_site_cfg to match the various other site_cfg.David Blaikie2012-09-041-4/+9
| | | | | | | | | This doesn't seem ideal, perhaps we could just keep the llvm_site_cfg and have other config (clang and clang-tools-extra) derive their site_cfg from that. Suggestions/complaints/ideas welcome. llvm-svn: 163171
* llvm-lit: Inject the lit module path at the beginning of sys.path, just in caseDaniel Dunbar2012-04-191-2/+3
| | | | | | the user has another lit somewhere. llvm-svn: 155131
* llvm-lit may be available with CMake.NAKAMURA Takumi2011-02-091-0/+2
| | | | llvm-svn: 125168
* llvm-lit may be able to invoke clang tests.NAKAMURA Takumi2011-02-091-0/+4
| | | | llvm-svn: 125167
* tests: Add an 'llvm-lit' tool (script), which gets generated as part of theDaniel Dunbar2010-08-021-0/+21
build and has the object build directory baked into it. This allows 'llvm-lit' to properly find the information needed to run the test suite in all cases, without requiring the user to have LLVM or 'lit' available in their PATH, for example. llvm-svn: 110000
OpenPOWER on IntegriCloud