Consider using cmake-presets instead of custom configuriation files

[Knitschi]

cmake 3.19 introduced the preset .json files for the same purpose for which I introduced my config.cmake files. Switching to default cmake solution would probably improve acceptance in the user base.

This ticket is about examining if cmakes preset files can replace the custom solution in CPFCMake and CPFBuildscripts and what would need to be done to implement it. We also have not yet removed the duplication of configuration information between the package manager configuration and the local configuration files.

[Knitschi]

Exploration Results:

• Visual Studio uses other settings than the CMake settings file. CMakePresets.json used by CMake vs. CMakeSettings.json used by Visual Studio.
• The CMakeSettings.json file contains the generate command line for running cmake, which is probably not included in cmake provided file. So in order to support Visual Studios CMake mode we would need both files.
• Is CMake mode worth the effort? Advantages -> no solution reloads, can use ninja. Disadvantages -> Target View is not exactly as the normal solution (switching between the two views is necessary), no re-build, requires VS specific settings file (same for VS code?), BuildVision plugin does not work.

[Knitschi]

Possible Tasks:

• Rewrite the 1_Configure.py script to generate a CMakeUserPresets.json file that inherits from a preset in the CMakePresets.json file.
• Modify the 3_Generate.py script to use the --preset option instead of the -C option.