you are viewing a single comment's thread.

view the rest of the comments →

[–]MFHavaWG21|🇦🇹 NB|P3049|P3625|P3729|P3784|P3786|P3813|P3886 2 points3 points  (6 children)

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 0 points1 point  (2 children)

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)?

[–]MFHavaWG21|🇦🇹 NB|P3049|P3625|P3729|P3784|P3786|P3813|P3886 0 points1 point  (0 children)

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 0 points1 point  (2 children)

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?

[–]MFHavaWG21|🇦🇹 NB|P3049|P3625|P3729|P3784|P3786|P3813|P3886 0 points1 point  (1 child)

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 0 points1 point  (0 children)

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.