MantisBT - CMake | |||||
| View Issue Details | |||||
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0015690 | CMake | CTest | public | 2015-08-07 16:41 | 2016-06-10 14:31 |
| Reporter | Clinton Stimpson | ||||
| Assigned To | Kitware Robot | ||||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | closed | Resolution | moved | ||
| Platform | OS | OS Version | |||
| Product Version | |||||
| Target Version | Fixed in Version | ||||
| Summary | 0015690: ctest doing one more undesirable run | ||||
| Description | I call ctest -VV -S my.ctest and it goes through my script, then decides to do one more configure/build/test, which I don't want. | ||||
| Steps To Reproduce | Use this ctest script: set(CTEST_SOURCE_DIRECTORY ${CMAKE_CURRENT_LIST_DIR}/src) set(CTEST_BINARY_DIRECTORY ${CMAKE_CURRENT_LIST_DIR}/build) set(CTEST_CMAKE_GENERATOR "Unix Makefiles") set(CTEST_PROJECT_NAME "all") set(CTEST_CONFIGURATION_TYPE "Release") set(CTEST_COMMAND "ctest") function(doit) ctest_start(Experimental) ctest_configure() ctest_build() endfunction() doit() | ||||
| Additional Information | Notice how I'm using a function(). If I change to a macro(), then the problem goes away. But I don't want to do that. A workaround is to add set(CTEST_RUN_CURRENT_SCRIPT OFF) at the bottom of my script (yuck). | ||||
| Tags | No tags attached. | ||||
| Relationships | |||||
| Attached Files | |||||
| Issue History | |||||
| Date Modified | Username | Field | Change | ||
| 2015-08-07 16:41 | Clinton Stimpson | New Issue | |||
| 2015-08-10 08:33 | Brad King | Note Added: 0039259 | |||
| 2016-06-10 14:29 | Kitware Robot | Note Added: 0042821 | |||
| 2016-06-10 14:29 | Kitware Robot | Status | new => resolved | ||
| 2016-06-10 14:29 | Kitware Robot | Resolution | open => moved | ||
| 2016-06-10 14:29 | Kitware Robot | Assigned To | => Kitware Robot | ||
| 2016-06-10 14:31 | Kitware Robot | Status | resolved => closed | ||
| Notes | |||||
|
|
|||||
|
|
||||
|
|
|||||
|
|
||||