CMake issueshttps://gitlab.kitware.com/cmake/cmake/-/issues2017-10-13T13:18:30-04:00https://gitlab.kitware.com/cmake/cmake/-/issues/14470CPACK_ZIP_COMPONENT_INSTALL does not work2017-10-13T13:18:30-04:00Kitware RobotCPACK_ZIP_COMPONENT_INSTALL does not workThis issue was created automatically from an original [Mantis Issue](https://cmake.org/Bug/view.php?id=14470). Further discussion may take place here.This issue was created automatically from an original [Mantis Issue](https://cmake.org/Bug/view.php?id=14470). Further discussion may take place here.https://gitlab.kitware.com/cmake/cmake/-/issues/15782create_test_sourcelist docs miss a `const` that is required with MSVC2019-11-08T08:51:28-05:00Kitware Robotcreate_test_sourcelist docs miss a `const` that is required with MSVCThis issue was created automatically from an original [Mantis Issue](https://cmake.org/Bug/view.php?id=15782). Further discussion may take place here.This issue was created automatically from an original [Mantis Issue](https://cmake.org/Bug/view.php?id=15782). Further discussion may take place here.https://gitlab.kitware.com/cmake/cmake/-/issues/23855create_test_sourcelist: fails to compile test driver when path contains tilde2022-08-18T07:57:51-04:00Klaas Spellercreate_test_sourcelist: fails to compile test driver when path contains tildeWhen storing a project under a path which contains a tilde (`~`) in the pathname `create_test_sourcelist` fails to compile.
Apple uses (or can use?) a tilde in the pathname of a mounted iCloud Drive. I have a code folder stored on thei...When storing a project under a path which contains a tilde (`~`) in the pathname `create_test_sourcelist` fails to compile.
Apple uses (or can use?) a tilde in the pathname of a mounted iCloud Drive. I have a code folder stored on their for backup and for easy access over several machines.
The issue appears to be around line 92 in `CMake/Source/cmCreateTestSourceList.cxx` where several illegal characters are replaced by underscore characters but the tilde is not included in the list.
See https://gitlab.kitware.com/cmake/cmake/-/blob/v3.24.0/Source/cmCreateTestSourceList.cxx#L92 for the location of the issue.
Adding `std::replace(func_name.begin(), func_name.end(), '~', '_');` at line 93 would allow projects to be stored under paths containing a `~`.https://gitlab.kitware.com/cmake/cmake/-/issues/16162Cross reference CXX_STANDARD and CXX_EXTENSIONS2018-02-20T16:28:55-05:00Robert MaynardCross reference CXX_STANDARD and CXX_EXTENSIONSUpdate the documentation for ```C/CXX_STANDARD``` (https://cmake.org/cmake/help/latest/prop_tgt/CXX_STANDARD.html) to include a cross reference to the ```C/CXX_EXTENSIONS``` page.Update the documentation for ```C/CXX_STANDARD``` (https://cmake.org/cmake/help/latest/prop_tgt/CXX_STANDARD.html) to include a cross reference to the ```C/CXX_EXTENSIONS``` page.3.6.0Gregor JasnyGregor Jasnyhttps://gitlab.kitware.com/cmake/cmake/-/issues/22129ctest --overwrite option is not well documented2021-04-29T08:46:10-04:00Cristian Morales Vegactest --overwrite option is not well documentedBoth https://cmake.org/cmake/help/latest/manual/ctest.1.html and ctest --help say `--overwrite` is an option that takes no arguments.
I didn't even understand what the option did until I found `overwriteConfigurationFile` in https://cma...Both https://cmake.org/cmake/help/latest/manual/ctest.1.html and ctest --help say `--overwrite` is an option that takes no arguments.
I didn't even understand what the option did until I found `overwriteConfigurationFile` in https://cmake.org/cmake/help/latest/manual/cmake-presets.7.html#test-preset.https://gitlab.kitware.com/cmake/cmake/-/issues/17141CTest fixtures not added when selecting a subset of tests2017-08-10T09:23:24-04:00Sergiu DeitschCTest fixtures not added when selecting a subset of testsA simple project:
```cmake
cmake_minimum_required (VERSION 3.7)
project (foo)
enable_testing ()
add_test (NAME test_setup COMMAND ${CMAKE_COMMAND} -E echo setup)
add_test (NAME test_cleanup COMMAND ${CMAKE_COMMAND} -E echo cleanup)
add...A simple project:
```cmake
cmake_minimum_required (VERSION 3.7)
project (foo)
enable_testing ()
add_test (NAME test_setup COMMAND ${CMAKE_COMMAND} -E echo setup)
add_test (NAME test_cleanup COMMAND ${CMAKE_COMMAND} -E echo cleanup)
add_test (NAME test_foo COMMAND ${CMAKE_COMMAND} -E echo "needs fixture")
set_tests_properties (test_setup PROPERTIES FIXTURES_SETUP test_foo)
set_tests_properties (test_cleanup PROPERTIES FIXTURES_CLEANUP test_foo)
```
Executing `$ ctest -R test_foo -V` does not add the setup/cleanup fixtures to the selected test:
```
UpdateCTestConfiguration from :/home/sergiu/Projects/ctest-test/build/DartConfiguration.tcl
UpdateCTestConfiguration from :/home/sergiu/Projects/ctest-test/build/DartConfiguration.tcl
Test project /home/sergiu/Projects/ctest-test/build
Constructing a list of tests
Done constructing a list of tests
Updating test list for fixtures
Added 0 tests to meet fixture requirements
Checking test dependency graph...
Checking test dependency graph end
test 3
Start 3: test_foo
3: Test command: /home/sergiu/Projects/CMake/build/install/bin/cmake "-E" "echo" "needs fixture"
3: Test timeout computed to be: 9.99988e+06
3: needs fixture
1/1 Test #3: test_foo ......................... Passed 0.00 sec
The following tests passed:
test_foo
100% tests passed, 0 tests failed out of 1
Total Test time (real) = 0.00 sec
```Craig ScottCraig Scotthttps://gitlab.kitware.com/cmake/cmake/-/issues/19712CTest: Add PARALLEL_LEVEL argument to ctest_build()2021-05-05T10:12:41-04:00Daniel PfeiferCTest: Add PARALLEL_LEVEL argument to ctest_build()The `ctest_test()` command supports this argument.
Since `ctest_build()` uses `cmake --build` under the hood, and `cmake --build` supports `--parallel`, it shouldn't be that hard to add support for this argument to `ctest_build()`.The `ctest_test()` command supports this argument.
Since `ctest_build()` uses `cmake --build` under the hood, and `cmake --build` supports `--parallel`, it shouldn't be that hard to add support for this argument to `ctest_build()`.3.21.0https://gitlab.kitware.com/cmake/cmake/-/issues/12623ctest_build() with Visual Studio 2008 Generator calling wrong Solution name.2017-10-13T13:18:31-04:00Kitware Robotctest_build() with Visual Studio 2008 Generator calling wrong Solution name.This issue was created automatically from an original [Mantis Issue](https://cmake.org/Bug/view.php?id=12623). Further discussion may take place here.This issue was created automatically from an original [Mantis Issue](https://cmake.org/Bug/view.php?id=12623). Further discussion may take place here.https://gitlab.kitware.com/cmake/cmake/-/issues/11774ctest_test causes an error when no tests are found2022-07-27T15:40:10-04:00Kitware Robotctest_test causes an error when no tests are foundThis issue was created automatically from an original [Mantis Issue](https://cmake.org/Bug/view.php?id=11774). Further discussion may take place here.This issue was created automatically from an original [Mantis Issue](https://cmake.org/Bug/view.php?id=11774). Further discussion may take place here.3.17.0https://gitlab.kitware.com/cmake/cmake/-/issues/15921CUDA_nvcuvid_LIBRARY and CUDA_nvcuvenc_LIBRARY is never set to anything in Fi...2019-11-27T14:49:23-05:00Kitware RobotCUDA_nvcuvid_LIBRARY and CUDA_nvcuvenc_LIBRARY is never set to anything in FindCUDA.cmakeThis issue was created automatically from an original [Mantis Issue](https://cmake.org/Bug/view.php?id=15921). Further discussion may take place here.This issue was created automatically from an original [Mantis Issue](https://cmake.org/Bug/view.php?id=15921). Further discussion may take place here.https://gitlab.kitware.com/cmake/cmake/-/issues/14829DEPENDS: Specifies that this test should only be run after the specified list...2022-07-27T15:37:27-04:00Kitware RobotDEPENDS: Specifies that this test should only be run after the specified list of tests.This issue was created automatically from an original [Mantis Issue](https://cmake.org/Bug/view.php?id=14829). Further discussion may take place here.This issue was created automatically from an original [Mantis Issue](https://cmake.org/Bug/view.php?id=14829). Further discussion may take place here.https://gitlab.kitware.com/cmake/cmake/-/issues/15160Different timeout for test and memcheck2018-02-21T09:08:47-05:00Kitware RobotDifferent timeout for test and memcheckThis issue was created automatically from an original [Mantis Issue](https://cmake.org/Bug/view.php?id=15160). Further discussion may take place here.This issue was created automatically from an original [Mantis Issue](https://cmake.org/Bug/view.php?id=15160). Further discussion may take place here.https://gitlab.kitware.com/cmake/cmake/-/issues/19711Display test exit status when tests fails after running `make test`2021-10-21T21:22:32-04:00Michal NovotnýDisplay test exit status when tests fails after running `make test`I am using cmake add_test directive to add a test to my project. From the test i exit with non-zero status code when there is something wrong. I check multiple things in the test and exit with a different status code for each check if it...I am using cmake add_test directive to add a test to my project. From the test i exit with non-zero status code when there is something wrong. I check multiple things in the test and exit with a different status code for each check if it fails. But when i run `make test` or `ctest -V` i don't see the exit status number (the return code) in the output so i don't know which test failed. It would be good to display that information in the test output.https://gitlab.kitware.com/cmake/cmake/-/issues/16556doc: Update spec for file(GENERATE OUTPUT)2017-07-12T11:33:23-04:00Ilia Kdoc: Update spec for file(GENERATE OUTPUT)Hi guys!
Could you please add a note in the [spec](https://cmake.org/cmake/help/latest/command/file.html) for `file(GENERATE OUTPUT)` that the files will be generated after all configurations are completed, right before cmake exit?
It...Hi guys!
Could you please add a note in the [spec](https://cmake.org/cmake/help/latest/command/file.html) for `file(GENERATE OUTPUT)` that the files will be generated after all configurations are completed, right before cmake exit?
It would save a few hours for someone other than me.Craig ScottCraig Scotthttps://gitlab.kitware.com/cmake/cmake/-/issues/13204Docs don't say what happens to symlinks in copy_directory2019-03-13T10:19:24-04:00Kitware RobotDocs don't say what happens to symlinks in copy_directoryThis issue was created automatically from an original [Mantis Issue](https://cmake.org/Bug/view.php?id=13204). Further discussion may take place here.This issue was created automatically from an original [Mantis Issue](https://cmake.org/Bug/view.php?id=13204). Further discussion may take place here.https://gitlab.kitware.com/cmake/cmake/-/issues/16170Docs should mention that CMAKE_TOOLCHAIN_FILE does not have access to the cache2020-11-04T03:51:03-05:00Ian MerinDocs should mention that CMAKE_TOOLCHAIN_FILE does not have access to the cacheI am unsure if this is intended behavior.
When setting the CMAKE_SYSROOT variable in a Toolchain file, cache variables defined inside the Toolchain file are expanded in the --sysroots option passed to the compiler, but cache variables...I am unsure if this is intended behavior.
When setting the CMAKE_SYSROOT variable in a Toolchain file, cache variables defined inside the Toolchain file are expanded in the --sysroots option passed to the compiler, but cache variables defined on the command line do not expand
Example:
In the Toolchain file:
set(internal-dir xyz)
(set CMAKE_SYSROOT ${internal-dir}/${external-dir}/example)
On the command line:
cmake -Dexternal-dir=abc -DCMAKE_TOOLCHAIN_FILE=Toolchain.cmake
When trying to compile, --sysroot will be 'xyz//example', but the value of ${external-dir} is indeed set as abc confirmed by printing the value of ${external-dir}.https://gitlab.kitware.com/cmake/cmake/-/issues/16203Document ccmake keybindings2022-04-08T09:58:13-04:00Ben BoeckelDocument ccmake keybindingsCurrently there's no documentation for how to actually use ccmake (particularly what keys are available).Currently there's no documentation for how to actually use ccmake (particularly what keys are available).https://gitlab.kitware.com/cmake/cmake/-/issues/16264Document how kwrobot checks MRs2018-02-20T16:28:55-05:00Ben BoeckelDocument how kwrobot checks MRskwrobot checking each commit seems to be tripping contributors up; we should document what is going on (and a failed `Do: check` should mention how to fix things; see: utils/rust-ghostflow#5).
Cc: @brad.king kwrobot checking each commit seems to be tripping contributors up; we should document what is going on (and a failed `Do: check` should mention how to fix things; see: utils/rust-ghostflow#5).
Cc: @brad.king Ben BoeckelBen Boeckelhttps://gitlab.kitware.com/cmake/cmake/-/issues/16863Document list quoting and expansion in generator expression usage2017-05-09T14:39:47-04:00Brad KingDocument list quoting and expansion in generator expression usageThe [cmake-generator-expressions(7)](https://cmake.org/cmake/help/v3.8/manual/cmake-generator-expressions.7.html) manual should explain how to deal with `;`-lists:
* Mention `COMMAND_EXPAND_LISTS` for post-genex list expansion in custom...The [cmake-generator-expressions(7)](https://cmake.org/cmake/help/v3.8/manual/cmake-generator-expressions.7.html) manual should explain how to deal with `;`-lists:
* Mention `COMMAND_EXPAND_LISTS` for post-genex list expansion in custom commands.
* Suggest quoting genex arguments to commands like `target_link_libraries` when they contain `${var}` references that may have lists.https://gitlab.kitware.com/cmake/cmake/-/issues/16661Documentation about make-style variable references is misleading2017-05-04T16:23:48-04:00Michael MalteseDocumentation about make-style variable references is misleadingSince at least 3.0, the [documentation on syntax](https://cmake.org/cmake/help/v3.0/manual/cmake-language.7.html#syntax) has read:
> To support legacy CMake code, unquoted arguments may also contain double-quoted strings (`"..."`, pos...Since at least 3.0, the [documentation on syntax](https://cmake.org/cmake/help/v3.0/manual/cmake-language.7.html#syntax) has read:
> To support legacy CMake code, unquoted arguments may also contain double-quoted strings (`"..."`, possibly enclosing horizontal whitespace), and make-style variable references (`$(MAKEVAR)`).
I tried a simple CMake project on 3.7.2, 3.5.0, and 2.8.12.1:
```cmake
cmake_minimum_required(VERSION 2.6)
project(foo)
set(SOURCES main.cpp)
add_executable(main $(SOURCES))
```
and on all versions I get the following error:
```
CMake Error at CMakeLists.txt:6 (add_executable):
Cannot find source file:
$(SOURCES)
Tried extensions .c .C .c++ .cc .cpp .cxx .m .M .mm .h .hh .h++ .hm .hpp
.hxx .in .txx
CMake Error: CMake can not determine linker language for target: main
CMake Error: Cannot determine link language for target "main".
```