CMake presets

On project opening, CLion detects all build and configure presets in CMakePresets.json and CMakeUserPresets.json files under the project root and loads them automatically into the dedicated CMake profiles in read-only mode.

tip

In case you don't want the presets to be converted into CMake profiles automatically, go to Settings | Advanced Settings and clear the Enable CMake Presets integration checkbox. This will also delete the existing presets-based profiles upon the next CMake reload or project reopening.

To view the loaded presets, go to Settings | Build, Execution, Deployment | CMake or use the View link in the notification dialog:

• All new presets are disabled by default, unless you have already loaded and enabled them before (CLion matches them by name).

• All previously loaded presets are removed if they are not present in the CMakePresets.json or CMakeUserPresets.json files.

note

Presets loading is also triggered by the Reset Cache and Reload and Load CMake Project actions.

There are two options you can use to edit the imported presets:

• Edit a copy of a presets-based CMake profile

• Modify the corresponding JSON files in the editor

Changing the toolchain

By default, the loaded preset is linked to the default CLion toolchain.

To set one of the already configured toolchains, modify the vendor-specific field of the configure preset.

For example, use the following code to switch to a toolchain called Clang10:

"vendor": {
    "jetbrains.com/clion": {
      "toolchain": "Clang10"
    }
}

As a result, the Clang10 toolchain will be assigned to the loaded preset:

On Windows, if you are working with the MSVC toolchain, the architecture and toolset properties from the configure preset will be fetched to CMake options as well: