CMakePresets.json support?

[eHonnef]

Hello, currently I'm using a project that contains a CMakePresets.json file.

I'm aware that you can create a build system that invokes cmake, but that demands that I manually write the build system with every preset in the file.

What I like about this package is that the "configure" will create the build system for us.

Is there a way to do that but using the json file?

[Servomex-ivisser]

Can I add my vote to this request?

We build our code base for many platforms, including various STM32 MicroController Units (MCU).
Each MCU requires its own compiler defines and options which we carefully manage through CMake presets.
That presets can inherit from others is a massive gain to us.

I could of course use Visual Studio Code as my editor and build platform, but I much prefer the "lighweigthtedness" of Sublime Text (ST).

It's not a massive PITA to switch between command line and ST, but if we could build the target through selecting a preset name from within ST, then this would be quite a powerful feature. To me at least.

[lulle2007200]

I have added support for CMake presets in my fork here: github.com/lulle2007200/CMakeBuilder

Currently it works as follows:

• Checks if there is a CMakePresets.json next to CMakeLists.txt in the root folder
• If yes, loads the configure and build presets and asks the user to select a configure preset (or none) via quick panel
• If none is selected, preset is not used and it behaves as if there were none
• If preset is selected, the selected preset is used for CMake configure. The remaining CMakeBuilder settings act as overrides to the selected preset. If a generator is specified both in the preset and in settings, the one from settings is used and a warning is logged (the settings in the preset might be incompatible with the overriden generator). If a build folder is specified in settings, and a preset is selected, and the selected configure preset specifies a binaryDir and there is atleast one build preset for the selected configure preset, CMakeBuilder will fail. This is because when building with a build preset, and the associated configure preset has a binaryDir specified, CMake will unconditionally look for build files in that folder, so configuring with the build folder overwritten makes no sense in that case.
• If there are build presets, a build system for each preset will be added named "Preset - [name of the build preset]"
• The default build systems are still created, even when a build preset is present

Currently my fork includes a few libraries it depends on side by side. This is because they are either not available via packagecontrol or the version is too outdated/has bugs.

If there is interest in merging it, i can bring my fork up to a mergeable state.

A few things im not too sure about:

• Does it make sense to still generate the default build targets when build presets are present?
• Should the CMakeBuilder settings be ignored instead of acting as override when a preset is used? Especially because build folder can only be overriden in certain circumstances, see above.