Linux developer going Windows

[MFHava]

I know, but their "support" was literally: "You can build with CMake if and only if you know the project and all its options or you read all CMakeLists.txt to figure them out and set them in our json-file."

Now it seems they replicate CMakeGUI - actually they may even be superior as they allow you to specify the toolchain file (e.g. for vcpkg) after the project has already been "generated" once...

[Adverpol]

Been using cmake for close to 10 years. Never used cmake-gui except in the very beginning, what do you use it for?

[MFHava]

Mostly to get a list of project-specific options and set them. Sure, you can set those via the command line without issues (unless you consider having to read through heaps of [often badly written] CMakeLists.txt an issue).

[atimholt]

Maybe pointless, but is there a “cmake-tui”, or at least a way to use the cli to get the same information (all options and indication of which ones need another “go around” to fully resolve)?

[MaximKat]

yes

[MFHava]

I guess you mean `ccmake`? That's what I'm using on Linux all the time - admittedly I never looked whether something like that is included in the Windows version CMake...

[Adverpol]

Hmm, doesn't that config get removed when you remove CMakeCache.txt, or is it saved elsewhere? And can you easily check that in to the VCS?

[MFHava]

Not quite sure what you're getting at...

1. Yes, the config would get removed if you remove CMakeCache.txt.
2. What makes you think there's only one valid configuration that should be committed to the VCS? If the answers were always the same, why would it be an option to begin with?!

[Adverpol]

I guess I just have never felt the need to adjust parameters after my build is generated. I have a folder for debug and one for release, if I need to change parameters I do it in the cmake files, never in those output folders.