ctest

CTest can not find executable file

随声附和 提交于 2021-01-28 10:50:48
问题 I have a question about starting the ctest. As I can understand that ctest uses CTestTestfile.cmake for the beginning of the unit test. What is the executable file? Why does ctest find it as *.exe if it is a CTestTestfile.cmake? What is wrong in my actions? I have a folder Prj: and folder /build with cmake output (CTestTestfile.cmake is here) as well as all ctest,cmake , etc. programs with their dll (is it right?). Here is the text of CMakeLists.txt file: cmake_minimum_required(VERSION 2.8)

Replace ctest command with “ctest --output-on-failure” permanently for a specific project in CMakeLists.txt

雨燕双飞 提交于 2020-07-26 16:59:58
问题 I have found that generic ctest command doesn't give much information about the tests, so I would like to add ctest --output-on-failure but not have the users to worry about the flag. I want them just to cmake , make the project and run ctest and it should run ctest with the --output-on-failure flag. Is it possible to do that in CMakeLists.txt? EDIT: Output of env CTEST_OUTPUT_ON_FAILURE=1 make test 4/13 Test #4: TEST_SSSP ........................***Failed Required regular expression not

Replace ctest command with “ctest --output-on-failure” permanently for a specific project in CMakeLists.txt

自闭症网瘾萝莉.ら 提交于 2020-07-26 16:57:17
问题 I have found that generic ctest command doesn't give much information about the tests, so I would like to add ctest --output-on-failure but not have the users to worry about the flag. I want them just to cmake , make the project and run ctest and it should run ctest with the --output-on-failure flag. Is it possible to do that in CMakeLists.txt? EDIT: Output of env CTEST_OUTPUT_ON_FAILURE=1 make test 4/13 Test #4: TEST_SSSP ........................***Failed Required regular expression not

Replace ctest command with “ctest --output-on-failure” permanently for a specific project in CMakeLists.txt

末鹿安然 提交于 2020-07-26 16:56:38
问题 I have found that generic ctest command doesn't give much information about the tests, so I would like to add ctest --output-on-failure but not have the users to worry about the flag. I want them just to cmake , make the project and run ctest and it should run ctest with the --output-on-failure flag. Is it possible to do that in CMakeLists.txt? EDIT: Output of env CTEST_OUTPUT_ON_FAILURE=1 make test 4/13 Test #4: TEST_SSSP ........................***Failed Required regular expression not

Replace ctest command with “ctest --output-on-failure” permanently for a specific project in CMakeLists.txt

时间秒杀一切 提交于 2020-07-26 16:56:31
问题 I have found that generic ctest command doesn't give much information about the tests, so I would like to add ctest --output-on-failure but not have the users to worry about the flag. I want them just to cmake , make the project and run ctest and it should run ctest with the --output-on-failure flag. Is it possible to do that in CMakeLists.txt? EDIT: Output of env CTEST_OUTPUT_ON_FAILURE=1 make test 4/13 Test #4: TEST_SSSP ........................***Failed Required regular expression not

Replace ctest command with “ctest --output-on-failure” permanently for a specific project in CMakeLists.txt

眉间皱痕 提交于 2020-07-26 16:54:24
问题 I have found that generic ctest command doesn't give much information about the tests, so I would like to add ctest --output-on-failure but not have the users to worry about the flag. I want them just to cmake , make the project and run ctest and it should run ctest with the --output-on-failure flag. Is it possible to do that in CMakeLists.txt? EDIT: Output of env CTEST_OUTPUT_ON_FAILURE=1 make test 4/13 Test #4: TEST_SSSP ........................***Failed Required regular expression not

Do not expand CMake list variable

筅森魡賤 提交于 2020-04-16 06:04:09
问题 I have a CMake script that runs some tests via add_test() , running under Windows (Server 2008, don't ask) in CMake 3.15. When these tests are called, the PYTHONPATH environment variable in the environment they run in seems to get reset to the environment default, and doesn't contain some paths that it needs to. I therefore need to set PYTHONPATH when the tests are run to the value of the $ENV{PYTHONPATH} variable when CMake runs. This has a number of semicolon-separated paths, so CMake