CMakePresets.json broke in new nRF Connect for VS Code version

Hi

We are using the CMakePresets.json file for different variations of our firmware. Since the latest update (2025.4.106) the build configuration interface changed a bit (now allowing to select the toolchain and SDK per build). When hitting `+ Add build configuration` and then selecting a CMakePreset, it doesn't fill out the preset anymore. However, if you select a Kconfig fragment, it then fills all the kconfig fragments from the preset.

The behaviour is the same for me and my colleague. So we assumed that the CMakePreset syntax was deprecated, but removing the old CMakePreset.json file, then manually configuring the build configuration and saving the new build configuration as a preset shows the same behaviour.

Best regards,

Alan

Parents
  • Hello,

    Thank you for reporting. Can you please share your CMakePresets.json file?

    Best regards,

    Edvin

  • {
        "version": 2,
        "cmakeMinimumRequired": {
            "major": 3,
            "minor": 20
        },
        "configurePresets": [
            {
                "name": "build_prod_CAT_M1",
                "displayName": "Build for Thingy91 nRF9160 Non Secure",
                "generator": "Ninja",
                "binaryDir": "${sourceDir}/current_build",
                "cacheVariables": {
                    "NCS_TOOLCHAIN_VERSION": "NONE",
                    "BOARD": "thingy91_nrf9160_ns",
                    "CONF_FILE": "prj.conf",
                    "EXTRA_CONF_FILE": "overlay-x.conf;overlay-VERSION-x-CAT-M1.conf;overlay-x-CAT-M1.conf",
                    "DTC_OVERLAY_FILE": "boards/x.overlay",
                    "EXTRA_DTC_OVERLAY_FILE": "boards/x_rake.overlay"
                }
            },
            {
                "name": "build_x_prod_NB_IOT",
                "displayName": "Build for Thingy91 nRF9160 Non Secure",
                "generator": "Ninja",
                "binaryDir": "${sourceDir}/current_build",
                "cacheVariables": {
                    "NCS_TOOLCHAIN_VERSION": "NONE",
                    "BOARD": "thingy91_nrf9160_ns",
                    "CONF_FILE": "prj.conf",
                    "EXTRA_CONF_FILE": "overlay-x-x.conf;overlay-x-NB-IOT.conf;overlay-x-VERSION-DAMO-NB-IOT.conf",
                    "DTC_OVERLAY_FILE": "boards\\x.overlay",
                    "EXTRA_DTC_OVERLAY_FILE": "boards\\x.overlay"
                }
            }
        ]
    }

    Hi Edvin

    Here you have the content of the original CMakePresets.json file. But as mentioned, deleting/renaming the file and saving a new preset from the UI also generates a CMakePresets.json file that doesn't work.

    best regards,

    Alan

  • Hello Alan,

    Thank you. Our VS Code team says that they identified the issue, and that they have patched it, and it will be included in the next release. Although, we currently don't know exactly when the next release will happen. Until then, you can use the previous version of the VS Code extension, if you need this functionality right now.

    Best regards,

    Edvin

  • Fair enough, can live without it for now, just thought I'd report the bug Slight smile

Reply Children
Related