CMake issueshttps://gitlab.kitware.com/cmake/cmake/-/issues2024-03-25T13:56:38-04:00https://gitlab.kitware.com/cmake/cmake/-/issues/25817cmake-gui doesn't consider a configure preset "valid" unless a generator is s...2024-03-25T13:56:38-04:00Richard Thomsoncmake-gui doesn't consider a configure preset "valid" unless a generator is specifiedThe documentation specifically states that the `generator` field may be omitted:
> In version 3 or above, this field may be omitted to fall back to regular generator discovery procedure.
This minimal configure preset doesn't show as 'v...The documentation specifically states that the `generator` field may be omitted:
> In version 3 or above, this field may be omitted to fall back to regular generator discovery procedure.
This minimal configure preset doesn't show as 'valid' in cmake-gui and is disabled.
```
{
"version": 5,
"cmakeMinimumRequired": {
"major": 3,
"minor": 23,
"patch": 0
},
"configurePresets": [
{
"name": "default",
"displayName": "Configure with default settings"
}
]
}
```
If I add a `generator` field, then cmake-gui considers it valid:
```
{
"version": 5,
"cmakeMinimumRequired": {
"major": 3,
"minor": 23,
"patch": 0
},
"configurePresets": [
{
"name": "default",
"displayName": "Configure with default settings",
"generator": "Visual Studio 17 2022"
}
]
}
```
Diagnostics about 'malformed' presets are an area where both the command-line tool and the GUI tool need improvement. The GUI is completely silent about whatever it considers to be the problem and the command-line tool often just says 'invalid' without giving any information about the context of the encountered error.https://gitlab.kitware.com/cmake/cmake/-/issues/25446ccmake segfault on generation2023-11-30T09:03:55-05:00Mathieu Westphal (Kitware)ccmake segfault on generation`ccmake` segfault on generation of a specific project.
`cmake` does not segfault.
Steps to reproduce:
- install VTK
-
```
git clone https://github.com/f3d-app/f3d
cd f3d
mkdir build
cd build
ccmake ../
c
c
g
```
- segfault
It happe...`ccmake` segfault on generation of a specific project.
`cmake` does not segfault.
Steps to reproduce:
- install VTK
-
```
git clone https://github.com/f3d-app/f3d
cd f3d
mkdir build
cd build
ccmake ../
c
c
g
```
- segfault
It happens in cmGeneratorTarget::IsImported(), because this->Target is **nullptr**.3.28.0Ben BoeckelBen Boeckelhttps://gitlab.kitware.com/cmake/cmake/-/issues/25386cmake-gui: crash on macOS after pasting string containing newline2023-11-03T12:46:06-04:00Sean McBridecmake-gui: crash on macOS after pasting string containing newlineI pasted a string that contained a newline into the CXXFLAGS field, then pressed Return, then clicked 'Configure', then it crashes.
It reproduces even.I pasted a string that contained a newline into the CXXFLAGS field, then pressed Return, then clicked 'Configure', then it crashes.
It reproduces even.https://gitlab.kitware.com/cmake/cmake/-/issues/25385cmake-gui: black theme, unreadable red background with gray text2023-11-04T19:50:36-04:00Crystal Hammercmake-gui: black theme, unreadable red background with gray text![06_15-30-08_](/uploads/299cfec8c1a8168becd04239bd199027/06_15-30-08_.jpg)
Hi. I've had this issue since many years.
It happens on Windows 10, with a black theme (based on high contrast one). If needed, theme is [on my website](https:...![06_15-30-08_](/uploads/299cfec8c1a8168becd04239bd199027/06_15-30-08_.jpg)
Hi. I've had this issue since many years.
It happens on Windows 10, with a black theme (based on high contrast one). If needed, theme is [on my website](https://cryham.tuxfamily.org/themes/#Windows_10).
It also happens on Debian with KDE. Probably any black theme, even Breeze Dark I think.
Two places are very annoying to read.
First, unreadable is the changed settings background, your red color. With gray text from system I think.
And second is that red text in messages area bottom. BTW, can I change the Courier font there on Windows?
As a general rule we should either set background and text colors or none of them. Or allow full program theme customization for all used colors.
I see no options for theme, colors or fonts in cmake-gui.https://gitlab.kitware.com/cmake/cmake/-/issues/25187cmake-gui: The text is too small2023-09-08T09:13:51-04:00dou fucmake-gui: The text is too smallMy Win11 system is configured with different dpi monitors(with scale 100% and 150), when dragging *cmake-gui* from one monitor to another, the text may become too small.
- normal:
![Snipaste_2023-08-15_11-12-16](/uploads/05ffe8756fc471...My Win11 system is configured with different dpi monitors(with scale 100% and 150), when dragging *cmake-gui* from one monitor to another, the text may become too small.
- normal:
![Snipaste_2023-08-15_11-12-16](/uploads/05ffe8756fc471a08e89ad5169eb8f31/Snipaste_2023-08-15_11-12-16.png)
- abnormal
![Snipaste_2023-08-15_11-12-36](/uploads/f0eac3660c3acd9005a930aba113f101/Snipaste_2023-08-15_11-12-36.png)3.28.0https://gitlab.kitware.com/cmake/cmake/-/issues/24593cmake-gui: "File" > "Delete cache" shows stale information if a Search query ...2023-03-13T14:16:26-04:00Menno Deij - van Rijswijkcmake-gui: "File" > "Delete cache" shows stale information if a Search query is activeI just noticed that when I have something typed into the Search text box, then choose File > Delete cache that the search query is not emptied, and that while backspacing in the textbox the stale information still shows until the search ...I just noticed that when I have something typed into the Search text box, then choose File > Delete cache that the search query is not emptied, and that while backspacing in the textbox the stale information still shows until the search text box is empty, then all cmake variables are cleared.
I would expect that once I choose `File` > `Delete cache`, that the gui would "reset" itself, emptying out all text boxes (search, output history) except the source/build paths.https://gitlab.kitware.com/cmake/cmake/-/issues/24343cmake-gui: does not adapt to dark mode on Windows2023-09-08T09:17:26-04:00Alexandre Baroncmake-gui: does not adapt to dark mode on WindowsI'm working with CMake 3.25.1 on Windows 10.
The OS theme is set on Dark mode systemwide, but CMake has still has its default grey and white theme.
I wonder why is that?
It seems to me that CMake should reflect the system theme, if I re...I'm working with CMake 3.25.1 on Windows 10.
The OS theme is set on Dark mode systemwide, but CMake has still has its default grey and white theme.
I wonder why is that?
It seems to me that CMake should reflect the system theme, if I refer to another issue opened 3 years ago : [dark mode for CMake GUI](https://gitlab.kitware.com/cmake/cmake/-/issues/19869).
It was closed 2 years ago, because it was supposedly fixed.
Is it a known issue? Or am I missing something?https://gitlab.kitware.com/cmake/cmake/-/issues/24248cmake-gui: Lots of runtime warnings while typing a regex with parentheses in ...2022-12-17T08:45:39-05:00Igor Kushnircmake-gui: Lots of runtime warnings while typing a regex with parentheses in the Search barWhen I enter an opening parenthesis into *cmake-gui*'s Search bar, it outputs hundreds? of identical warnings:
> QString(View)::contains(): called on an invalid QRegularExpression object (pattern is '(')
Probably can be fixed by checkin...When I enter an opening parenthesis into *cmake-gui*'s Search bar, it outputs hundreds? of identical warnings:
> QString(View)::contains(): called on an invalid QRegularExpression object (pattern is '(')
Probably can be fixed by checking `QRegularExpression::isValid()` and not calling `setFilterRegularExpression` if that returns `false`.3.26.0Kyle EdwardsKyle Edwardshttps://gitlab.kitware.com/cmake/cmake/-/issues/24034CMakePresets "toolchainFile" field ignored in cmake-gui2024-01-08T09:33:08-05:00Tim PattersonCMakePresets "toolchainFile" field ignored in cmake-guiWhen using the cmake-gui, the `CMakePresets.json` file below correctly selects and executes the toolchain file `toolchain.cmake`:
```json
{
"version": 3,
"cmakeMinimumRequired": { "major": 3, "minor": 24, "patch": 0 },
"configureP...When using the cmake-gui, the `CMakePresets.json` file below correctly selects and executes the toolchain file `toolchain.cmake`:
```json
{
"version": 3,
"cmakeMinimumRequired": { "major": 3, "minor": 24, "patch": 0 },
"configurePresets": [
{
"name": "default",
"generator": "Visual Studio 16 2019",
"cacheVariables": {
"CMAKE_TOOLCHAIN_FILE": "toolchain.cmake"
},
"toolchainFile": "toolchain.cmake"
}
],
"buildPresets": [
{
"name": "release",
"configurePreset": "default",
"configuration": "Release"
}
]
}
```
This only works because the `CMAKE_TOOLCHAIN_FILE` cache variable is being set. After removing this line from the CMakePresets file, the toolchain file is NOT set despite the fact that the `toolchainFile` field exists; the field appears to be ignored.Robert MaynardRobert Maynardhttps://gitlab.kitware.com/cmake/cmake/-/issues/23983cmake-gui: improve GUI feedback / keyboard navigation in table view2022-09-22T12:38:24-04:00ronso0cmake-gui: improve GUI feedback / keyboard navigation in table viewI'd like to use cmake-gui with keyboard only, though navigation/UX can be improeved IMO:
* missing focus highlight for pushbuttons
* didn't figure how to focus checkboxes/textedits in the table view with the keyboard
(once a checkbox...I'd like to use cmake-gui with keyboard only, though navigation/UX can be improeved IMO:
* missing focus highlight for pushbuttons
* didn't figure how to focus checkboxes/textedits in the table view with the keyboard
(once a checkbox was clicked the respective column has focus and other items can be focused and edited with arrow keys)
I'm working on Mixxx which is also built with Qt so I know my desktop theme supports focus highlight for standard dialog widgets, thus I wonder why it's not working in cmake-gui.
cmake-qt-gui 3.16.3-1ubuntu1
Ubuntu Studio 20.04 - xfce 4.14https://gitlab.kitware.com/cmake/cmake/-/issues/23966cmake-gui: macOS --install helper honors umask2022-09-16T11:10:47-04:00Andrew Wcmake-gui: macOS --install helper honors umaskWith fresh install of computer and CMake 3.24.2 (DMG for OSX 12.5.1)
Run command line tool install script (for /usr/local/bin)
Setup up super-simple CMake project:
% mkdir src
% touch empty.c
% cat > CMakeLists.txt
add...With fresh install of computer and CMake 3.24.2 (DMG for OSX 12.5.1)
Run command line tool install script (for /usr/local/bin)
Setup up super-simple CMake project:
% mkdir src
% touch empty.c
% cat > CMakeLists.txt
add_library( empty empty.c )
% cmake src
Now run cmake
% cmake src
CMake Error: Could not find CMAKE_ROOT !!!
CMake has most likely not been installed correctly.
Modules directory not found in
/usr/local/share/cmake-3.24
CMake Error: Error executing cmake::LoadCache(). Aborting.
zsh: exit 1 cmake srchttps://gitlab.kitware.com/cmake/cmake/-/issues/23965OS X: odd behaviour when selecting "How to install for command line use" from...2022-09-16T11:08:25-04:00Andrew WOS X: odd behaviour when selecting "How to install for command line use" from installed cmake-guiSteps to reproduce:
- download and install CMake (3.24.2) on OS X from .dmg
- run app (from Applications)
- choose "How to install for command line use"
- copy and execute command for "install symlinks to /usr/local/bin"
- quit CMake app...Steps to reproduce:
- download and install CMake (3.24.2) on OS X from .dmg
- run app (from Applications)
- choose "How to install for command line use"
- copy and execute command for "install symlinks to /usr/local/bin"
- quit CMake app
- from terminal, run "cmake-gui"
- GUI app starts
- choose "How to install for command line use"
Expected behaviour:
- same paths as last time
Actual behaviour
- source paths are now all /usr/local/bin (which if you ran the command again means you would replace the symlinks in /usr/local/bin with symlinks to the symlinks)
Impact: Minor, unless someone actually follows the instructions, in which case it breaks the install
Recommended behaviour: resolve symlinks and present the original file pathhttps://gitlab.kitware.com/cmake/cmake/-/issues/23859cmake-gui: buggy when compiled by MSVC 14.33 / VS 17.3 toolset2022-11-11T08:29:16-05:00Brad Kingcmake-gui: buggy when compiled by MSVC 14.33 / VS 17.3 toolsetAfter !7578 updated our CI to the MSVC 14.33 toolset (from VS 17.3), the `cmake-gui` built by our nightly packaging pipeline (published [here](https://cmake.org/files/dev/?C=M;O=D)), no longer works reliably. Configuring randomly fails ...After !7578 updated our CI to the MSVC 14.33 toolset (from VS 17.3), the `cmake-gui` built by our nightly packaging pipeline (published [here](https://cmake.org/files/dev/?C=M;O=D)), no longer works reliably. Configuring randomly fails with various unrepeatable errors in processing the `.cmake` language code. I've built several different versions of CMake in CI pipelines with MSVC 14.32 and 14.33 toolsets, and the distinction between the two MSVC versions is repeatable.
I suspect that the MSVC 14.33 toolset may be miscompiling Qt code in `cmake-gui` in a way that clobbers memory elsewhere in the process.3.25.0Brad KingBrad Kinghttps://gitlab.kitware.com/cmake/cmake/-/issues/23721cmake-gui removes 'UNINITIALIZED' cache variables2023-08-11T10:10:34-04:00Nagger Xcmake-gui removes 'UNINITIALIZED' cache variablesIf 'cmake -D FOO=ON' is called a cache entry for FOO gets created. (in cache file as: `FOO:UNINITIALIZED=ON` )
When cmake-gui with this build dir is started, the cache entry is not shown in the list of cache variable.
But more importan...If 'cmake -D FOO=ON' is called a cache entry for FOO gets created. (in cache file as: `FOO:UNINITIALIZED=ON` )
When cmake-gui with this build dir is started, the cache entry is not shown in the list of cache variable.
But more importantly: When 'generate' is pressed the cache entry is removed from the cache (file)!
Subsequent calls to cmake will not see FOO again.
If the type of FOO is given (-D FOO:String=ON) everything works as expected.https://gitlab.kitware.com/cmake/cmake/-/issues/23565cmake-gui: Fix non-ASCII characters on Windows with Qt62022-06-11T05:52:20-04:00Brad Kingcmake-gui: Fix non-ASCII characters on Windows with Qt6When built with Qt6, `cmake-gui` does not support non-ASCII characters on Windows.
See #23562 and https://gitlab.kitware.com/cmake/cmake/-/issues/23562#note_1193534.When built with Qt6, `cmake-gui` does not support non-ASCII characters on Windows.
See #23562 and https://gitlab.kitware.com/cmake/cmake/-/issues/23562#note_1193534.3.24.0https://gitlab.kitware.com/cmake/cmake/-/issues/23562cmake-gui: no longer opens paths with non-ASCII characters (ñ) on windows 102022-06-02T11:52:13-04:00Alberto Luacescmake-gui: no longer opens paths with non-ASCII characters (ñ) on windows 10This was working correctly in 3.18.4, but updating to 3.23.2 makes project configuration fail with
> CMake Error: The source directory "E:/alberto/tests/cmake espacios y e�es" does not exist.
Replacing the troubling directory name with...This was working correctly in 3.18.4, but updating to 3.23.2 makes project configuration fail with
> CMake Error: The source directory "E:/alberto/tests/cmake espacios y e�es" does not exist.
Replacing the troubling directory name with its short counterpart `cmakee~1` works, and cmake expands it again with a garbled result, `cmake espacios y eñes`, so I suspect is an issue of a latin-1 to utf-8 conversion.3.21.7Brad KingBrad Kinghttps://gitlab.kitware.com/cmake/cmake/-/issues/23363cmake-gui fails to re-enable UI widgets for CACHE variables when switching to...2022-03-29T12:53:13-04:00Marek Vojtkocmake-gui fails to re-enable UI widgets for CACHE variables when switching to <custom> presetcmake-gui replaces UI widgets (e.g. checkboxes) for `CACHE` variables whose values are set by a CMake preset:
![presetCleanDir](/uploads/c14f86f4e6ae3fd8f2e2cea923c07659/presetCleanDir.png)
While the user can modify the text values, th...cmake-gui replaces UI widgets (e.g. checkboxes) for `CACHE` variables whose values are set by a CMake preset:
![presetCleanDir](/uploads/c14f86f4e6ae3fd8f2e2cea923c07659/presetCleanDir.png)
While the user can modify the text values, they get reset the next time they click *Configure*.
However, when the user changes the preset to `<custom>` (while keeping the build / binary directory the same), the text values do not change back to UI widgets:
![presetReusedDir](/uploads/ed1265d95afae3bce5d2042942c690a9/presetReusedDir.png)
The user is still able to modify the text values and their modifications persist when they click *Configure*, but the experience is poor.
**cmake-gui should restore the UI widgets for all variables when the user changes the preset to `<custom>`** since they are now editable.
The experience should match the one when the user selects the `<custom>` preset at the beginning, in a clean build directory:
![customCleanDir](/uploads/e633d1ce10baf0a493755573e2204a8d/customCleanDir.png)
Overriding `CACHE` variables that were set by a preset is very easy on the command line (`cmake --preset MyPreset -DSetViaPreset=On`) and it would be great if cmake-gui made that easier than it is now.https://gitlab.kitware.com/cmake/cmake/-/issues/23345cmake-gui: Ugly non-ASCII characters with default font on Windows2022-03-28T08:56:10-04:00Tilman Vogelcmake-gui: Ugly non-ASCII characters with default font on WindowsWhen using CMake GUI on Windows and CMake output contains special characters, they are rendered with a different, too big font, see:
![image](/uploads/76046509e1e25653ff9f1d4c42ac4244/image.png)
This is with CMake 3.17.3.
Two question...When using CMake GUI on Windows and CMake output contains special characters, they are rendered with a different, too big font, see:
![image](/uploads/76046509e1e25653ff9f1d4c42ac4244/image.png)
This is with CMake 3.17.3.
Two questions:
- How can I change the font used?
- Could you change the default font to make special characters pretty?https://gitlab.kitware.com/cmake/cmake/-/issues/23341presets: Version 3 configure preset without a generator is greyed out in GUI2024-03-09T07:49:47-05:00Paweł Szramowskipresets: Version 3 configure preset without a generator is greyed out in GUI![Capture](/uploads/29127e7a46fdfe0c9b73bccdff3c6d44/Capture.PNG)
A configure preset without `generator` (optional in version 3) should not be greyed out in GUI. A generator will need to be specified anyway upon proceeding to `Configure...![Capture](/uploads/29127e7a46fdfe0c9b73bccdff3c6d44/Capture.PNG)
A configure preset without `generator` (optional in version 3) should not be greyed out in GUI. A generator will need to be specified anyway upon proceeding to `Configure`.
OS: Windows 10
CMake version: 3.22.3
CMakePresets.json:
```json
{
"version": 3,
"configurePresets": [
{
"name": "without-generator"
},
{
"name": "with-generator",
"generator": "Ninja"
}
]
}
```
CMakeLists.txt:
```cmake
cmake_minimum_required(VERSION 3.21)
project(CmakeGuiPresetsBug)
add_executable(CmakeGuiPresetsBug main.c)
```
main.c:
```c
int main() {
return 0;
}
```https://gitlab.kitware.com/cmake/cmake/-/issues/22797cmake-gui: window widgets not complete2021-10-26T11:15:42-04:00Ze Xun Yaocmake-gui: window widgets not complete![image](/uploads/03393f2637d59216a470b133311932d7/image.png)
As the image shows, I cannot see configure / open buttons, neither the variables of the project.
A normal panel looks like below.
<details><summary>Normal window screenshot...![image](/uploads/03393f2637d59216a470b133311932d7/image.png)
As the image shows, I cannot see configure / open buttons, neither the variables of the project.
A normal panel looks like below.
<details><summary>Normal window screenshot</summary>
![image](/uploads/9a8293793479a39dd840d391f4443707/image.png)
</details>
please tell me what happened and hot to solve, thanks....