CMake issueshttps://gitlab.kitware.com/cmake/cmake/-/issues2018-02-20T16:28:55-05:00https://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/16265Missing @CMAKE_Fortran_SYSROOT_FLAG_CODE@ within CMakeFortranCompiler.cmake.in2018-02-20T16:28:55-05:00Ghost UserMissing @CMAKE_Fortran_SYSROOT_FLAG_CODE@ within CMakeFortranCompiler.cmake.inHi All,
while calling 'cmake ./' in a build box the following messages...
```
-- Checking whether Fortran compiler has -isysroot
-- Checking whether Fortran compiler has -isysroot - yes
-- Checking whether Fortran compiler support...Hi All,
while calling 'cmake ./' in a build box the following messages...
```
-- Checking whether Fortran compiler has -isysroot
-- Checking whether Fortran compiler has -isysroot - yes
-- Checking whether Fortran compiler supports OSX deployment target flag
-- Checking whether Fortran compiler supports OSX deployment target flag - yes
```
...are printed because of two missing statements ...
```cmake
@CMAKE_Fortran_SYSROOT_FLAG_CODE@
@CMAKE_Fortran_OSX_DEPLOYMENT_TARGET_FLAG_CODE@
```
... in CMakeFortranCompiler.cmake.in (similar to CMakeCCompiler.cmake.in)
Could someone please add them?
Thanks in advance.3.7.0Brad KingBrad Kinghttps://gitlab.kitware.com/cmake/cmake/-/issues/16258Valid properties for get_cmake_property() no longer documented2018-02-20T16:28:55-05:00Craig ScottValid properties for get_cmake_property() no longer documentedThe documentation for the `get_cmake_property()` command changed between CMake 3.3 and 3.4. In that change, all the valid property names were removed and there's nowhere else in the CMake documentation which provides this information. As...The documentation for the `get_cmake_property()` command changed between CMake 3.3 and 3.4. In that change, all the valid property names were removed and there's nowhere else in the CMake documentation which provides this information. As a result, it's technically a complete mystery what property names one can use with `get_cmake_property()` if you're going only by the latest documentation.
As it turns out, `get_cmake_property(myVar COMPONENTS)` is the only way one can get a list of all the install components that have been defined. With the latest documentation, you'd never know this capability existed.3.7.0Brad KingBrad Kinghttps://gitlab.kitware.com/cmake/cmake/-/issues/16211Documentation on default value of CMAKE_INSTALL_PREFIX in Windows is not cor...2018-02-20T16:28:55-05:00Silvio TraversaroDocumentation on default value of CMAKE_INSTALL_PREFIX in Windows is not correctThe documentation of the `CMAKE_INSTALL_PREFIX` variables states that its default value in Windows is `C:/Program Files/` [1], but the default value is actually `C:/Program Files/${PROJECT_NAME}` [2] .
[1] : https://gitlab.kitware....The documentation of the `CMAKE_INSTALL_PREFIX` variables states that its default value in Windows is `C:/Program Files/` [1], but the default value is actually `C:/Program Files/${PROJECT_NAME}` [2] .
[1] : https://gitlab.kitware.com/cmake/cmake/blob/master/Help/variable/CMAKE_INSTALL_PREFIX.rst
[2] : https://gitlab.kitware.com/cmake/cmake/blob/master/Source/cmLocalGenerator.cxx#L240 3.7.0Brad KingBrad Kinghttps://gitlab.kitware.com/cmake/cmake/-/issues/16180find_package(Java) does not set Java_INCLUDE_DIRS2018-02-20T16:28:56-05:00Richard Walkerfind_package(Java) does not set Java_INCLUDE_DIRSDocumentation states that the following should be set by calling find_package(Java):
```
# Java_INCLUDE_DIRS - Full paths to all include dirs.
# Java_LIBRARIES - Full paths to all libraries.
```
They...Documentation states that the following should be set by calling find_package(Java):
```
# Java_INCLUDE_DIRS - Full paths to all include dirs.
# Java_LIBRARIES - Full paths to all libraries.
```
They are not. There is no reference to these other than in the comments in FindJava.cmake. Other variables set correctly.
Kind regards,
Richard.3.7.0https://gitlab.kitware.com/cmake/cmake/-/issues/15783ALIASED_TARGET property is always set2018-12-07T09:57:23-05:00Kitware RobotALIASED_TARGET property is always setThis issue was created automatically from an original [Mantis Issue](https://cmake.org/Bug/view.php?id=15783). Further discussion may take place here.This issue was created automatically from an original [Mantis Issue](https://cmake.org/Bug/view.php?id=15783). Further discussion may take place here.3.7.0Gregor JasnyGregor Jasnyhttps://gitlab.kitware.com/cmake/cmake/-/issues/14362Can't add attr directive to CPACK_RPM_USER_FILELIST (some symbols not allowed)2018-12-07T09:58:20-05:00Kitware RobotCan't add attr directive to CPACK_RPM_USER_FILELIST (some symbols not allowed)This issue was created automatically from an original [Mantis Issue](https://cmake.org/Bug/view.php?id=14362). Further discussion may take place here.This issue was created automatically from an original [Mantis Issue](https://cmake.org/Bug/view.php?id=14362). Further discussion may take place here.3.7.0https://gitlab.kitware.com/cmake/cmake/-/issues/14332cpack >= 2.8.2 DEB generator produces invalid .deb when long filenames are in...2018-12-07T09:58:22-05:00Kitware Robotcpack >= 2.8.2 DEB generator produces invalid .deb when long filenames are involvedThis issue was created automatically from an original [Mantis Issue](https://cmake.org/Bug/view.php?id=14332). Further discussion may take place here.
---
When project installed files have long filenames (e.g. doxygen generated files),...This issue was created automatically from an original [Mantis Issue](https://cmake.org/Bug/view.php?id=14332). Further discussion may take place here.
---
When project installed files have long filenames (e.g. doxygen generated files), cpack creates a .deb which cannot be installed because it's internal archive seems corrupted.
```console
$ tar xvzf cpack-bug.tar.gz
$ cd cpack-bug
$ mkdir build && cd build
$ cmake ..
$ cpack -G DEB
$ sudo dpkg -i cpack_bug*.deb
(Reading database ... 536878 files and directories currently installed.)
Unpacking cpack_bug (from cpack_bug-1.1.0-Linux.deb) ...
dpkg: error processing cpack_bug-1.1.0-Linux.deb (--install):
corrupted filesystem tarfile - corrupted package archive
Errors were encountered while processing:
cpack_bug-1.1.0-Linux.deb
```
[cpack-bug.tar.gz](/uploads/0052dbd663f1662100449432865d9b1e/cpack-bug.tar.gz)3.7.0Domen VrankarDomen Vrankarhttps://gitlab.kitware.com/cmake/cmake/-/issues/13810Confusing documentation for GET_CMAKE_PROPERTY2018-12-07T09:58:43-05:00Kitware RobotConfusing documentation for GET_CMAKE_PROPERTYThis issue was created automatically from an original [Mantis Issue](https://cmake.org/Bug/view.php?id=13810). Further discussion may take place here.
---
The documentation for GET_CMAKE_PROPERTY lists the properties VARIABLES, CAC...This issue was created automatically from an original [Mantis Issue](https://cmake.org/Bug/view.php?id=13810). Further discussion may take place here.
---
The documentation for GET_CMAKE_PROPERTY lists the properties VARIABLES, CACHE_VARIABLES, COMMANDS, MACROS, and COMPONENTS as able to be obtained using this command. However, in the properties help file, these properties are only listed under properties for help files. Furthermore, the GET_CMAKE_PROPERTY command can be used to obtain properties listed as being of global scope, but there is nothing said to indicate so in its documentation. This should all be clarified.
3.7.0Brad KingBrad Kinghttps://gitlab.kitware.com/cmake/cmake/-/issues/16624BLA_VENDOR documentation not rendered correctly in FindBLAS/FindLAPACK docume...2017-05-04T16:23:49-04:00Silvio TraversaroBLA_VENDOR documentation not rendered correctly in FindBLAS/FindLAPACK documentationThe documentation on the possible values of the `BLA_VENDOR` variable supported in `FindBLAS` and `FindLAPACK` is not rendered correctly (or a least, it is not rendered *nicely*):
* https://cmake.org/cmake/help/v3.7/module/FindBLAS.html
...The documentation on the possible values of the `BLA_VENDOR` variable supported in `FindBLAS` and `FindLAPACK` is not rendered correctly (or a least, it is not rendered *nicely*):
* https://cmake.org/cmake/help/v3.7/module/FindBLAS.html
* https://cmake.org/cmake/help/v3.7/module/FindLAPACK.html3.8.0Gregor JasnyGregor Jasnyhttps://gitlab.kitware.com/cmake/cmake/-/issues/16504CMAKE_CL_64 documentation error2017-05-04T16:23:52-04:00Braden McDanielCMAKE_CL_64 documentation errorThe documentation for the `CMAKE_CL_64` variable states:
> Set to `true` when using the 64-bit `cl` compiler from Microsoft.
This appears to be inaccurate in a couple of respects.
1. The value is either `1` or `0`; never `true`. (I ...The documentation for the `CMAKE_CL_64` variable states:
> Set to `true` when using the 64-bit `cl` compiler from Microsoft.
This appears to be inaccurate in a couple of respects.
1. The value is either `1` or `0`; never `true`. (I appreciate that CMake treats both `1` and `true` as logically true values; however, if this value is substituted somewhere that is not processed by CMake, the difference is material.)
2. The value is still `0` if one is using the 64-bit compiler to build 32-bit binaries. Similarly, the value is `1` if one is using the 32-bit compiler to build 64-bit binaries. In other words, the value changes based on whether one is building 64- or 32-bit binaries, not based on whether the compiler is a 64- or 32-bit application.3.8.0Brad KingBrad Kinghttps://gitlab.kitware.com/cmake/cmake/-/issues/16917CMAKE_CXX_COMPILER_VERSION is not documented2017-05-30T09:26:23-04:00Mateusz ĹoskotCMAKE_CXX_COMPILER_VERSION is not documentedThe following variables are not documented in 3.8.1 (including the current git master/stage docs)
* `CMAKE_CXX_COMPILER_VERSION`
* `CMAKE_C_COMPILER_VERSION`The following variables are not documented in 3.8.1 (including the current git master/stage docs)
* `CMAKE_CXX_COMPILER_VERSION`
* `CMAKE_C_COMPILER_VERSION`3.9.0Gregor JasnyGregor Jasnyhttps://gitlab.kitware.com/cmake/cmake/-/issues/14460AC_ARG_VARs ignored in CMAKE_FIND_PACKAGE macro in cmake.m42018-12-07T09:58:16-05:00Kitware RobotAC_ARG_VARs ignored in CMAKE_FIND_PACKAGE macro in cmake.m4This issue was created automatically from an original [Mantis Issue](https://cmake.org/Bug/view.php?id=14460). Further discussion may take place here.This issue was created automatically from an original [Mantis Issue](https://cmake.org/Bug/view.php?id=14460). Further discussion may take place here.3.9.0https://gitlab.kitware.com/cmake/cmake/-/issues/14335CMake does not error on duplicate else()2018-12-07T09:58:21-05:00Kitware RobotCMake does not error on duplicate else()This issue was created automatically from an original [Mantis Issue](https://cmake.org/Bug/view.php?id=14335). Further discussion may take place here.This issue was created automatically from an original [Mantis Issue](https://cmake.org/Bug/view.php?id=14335). Further discussion may take place here.3.9.0Gregor JasnyGregor Jasnyhttps://gitlab.kitware.com/cmake/cmake/-/issues/10749CMakeDetermineSystem.cmake gets the wrong O/S version on AIX 4 & 52018-10-03T19:05:30-04:00Kitware RobotCMakeDetermineSystem.cmake gets the wrong O/S version on AIX 4 & 5This issue was created automatically from an original [Mantis Issue](https://cmake.org/Bug/view.php?id=10749). Further discussion may take place here.This issue was created automatically from an original [Mantis Issue](https://cmake.org/Bug/view.php?id=10749). Further discussion may take place here.3.9.0Gregor JasnyGregor Jasnyhttps://gitlab.kitware.com/cmake/cmake/-/issues/16001"cmake -E copy_directory" do not display error when directory to copy is not ...2018-05-17T09:05:16-04:00Kitware Robot"cmake -E copy_directory" do not display error when directory to copy is not existsThis issue was created automatically from an original [Mantis Issue](https://cmake.org/Bug/view.php?id=16001). Further discussion may take place here.
---
Run Command and make sure that "dupa" directory is not exists:
```console
$ cma...This issue was created automatically from an original [Mantis Issue](https://cmake.org/Bug/view.php?id=16001). Further discussion may take place here.
---
Run Command and make sure that "dupa" directory is not exists:
```console
$ cmake -E copy_directory dupa target
```
Currently:
```
The copy_directory command will silently ignore, that "dupa" directory is not exists. Directory "target" will be created if not exists.
```
Expected:
```
The copy_directory command should display error, that "dupa" directory is not exists. Directory "target" will be created if not exists.
```
3.12.0Brad KingBrad Kinghttps://gitlab.kitware.com/cmake/cmake/-/issues/13371Ninja: ADDITIONAL_MAKE_CLEAN_FILES is not supported2019-05-15T09:46:20-04:00Kitware RobotNinja: ADDITIONAL_MAKE_CLEAN_FILES is not supportedThis issue was created automatically from an original [Mantis Issue](https://cmake.org/Bug/view.php?id=13371). Further discussion may take place here.This issue was created automatically from an original [Mantis Issue](https://cmake.org/Bug/view.php?id=13371). Further discussion may take place here.3.15.0Sebastian HoltermannSebastian Holtermannhttps://gitlab.kitware.com/cmake/cmake/-/issues/15874Add command line flag to force ctest to exit with non-zero code when no tests...2022-07-27T15:40:22-04:00Kitware RobotAdd command line flag to force ctest to exit with non-zero code when no tests are runThis issue was created automatically from an original [Mantis Issue](https://cmake.org/Bug/view.php?id=15874). Further discussion may take place here.This issue was created automatically from an original [Mantis Issue](https://cmake.org/Bug/view.php?id=15874). Further discussion may take place here.3.17.0https://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/8768.F not in Source Files group with Visual Fortran2019-10-24T08:04:52-04:00Kitware Robot.F not in Source Files group with Visual FortranThis issue was created automatically from an original [Mantis Issue](https://cmake.org/Bug/view.php?id=8768). Further discussion may take place here.
---
Fortran projects for Visual Studio put the .f under Source Files but leave the .F...This issue was created automatically from an original [Mantis Issue](https://cmake.org/Bug/view.php?id=8768). Further discussion may take place here.
---
Fortran projects for Visual Studio put the .f under Source Files but leave the .F files at the root of the project tree.
Can we have both .F and .f in the Source Files folder?
3.17.0