Build Preset values change slash to backslash

RE: Build Preset values change slash to backslash

Samruddhi Jadhav — Fri, 13 Mar 2026 11:32:26 GMT

Hi again,

The issue has been fixed. Thanks for letting us know. It will be in the recovery release.

Best Regards,

Samruddhi

RE: Build Preset values change slash to backslash

Samruddhi Jadhav — Tue, 10 Mar 2026 08:02:45 GMT

Hi,

A quick update. We are working on this issue internally in the team and will get back to you soon with an update.

Best Regards,

Samruddhi

RE: Build Preset values change slash to backslash

SvenSi — Tue, 03 Mar 2026 08:17:51 GMT

After checking the "Generate only", it is still not possible to use the "Generate" button.

Then after unchecking the "Generate only" the "Generate and Build" button can be used and the build is running as it should without problems.

RE: Build Preset values change slash to backslash

Samruddhi Jadhav — Mon, 02 Mar 2026 14:55:42 GMT

Hi,

Can you please try to use the preset, then check and uncheck the generate build option?

Best Regards,

Samruddhi

RE: Build Preset values change slash to backslash

SvenSi — Mon, 02 Mar 2026 12:58:29 GMT

If I add a new build configuration and choose one of the presets, then it is not possible to use the "Generate and Build" button. So there is no output.

As soon as I edit the file selection to the same file (select this from the list in the filename-field), it is possible to click the button and everything builds as it should.

Could you clarify which part is doing the conversion from the CMakePreset file to the settings which are set in the "add build-configuration" window? Is this a part of the nrfSDK (NCS) or is this part of the visual Studio extension?

RE: Build Preset values change slash to backslash

Samruddhi Jadhav — Mon, 02 Mar 2026 12:10:46 GMT

Hi,

Are you seeing the backslash being applied but in the build command it's changing to the right format so the build is able to pass? If not, can you please provide the build logs?

Have you also made sure that the file from the preset isn't missing?

Best Regards,

Samruddhi

RE: Build Preset values change slash to backslash

Samruddhi Jadhav — Mon, 02 Mar 2026 11:47:31 GMT

Hi again,

I have reported the issue to the team and will get back to you soon with an update once this has been fixed.

Best Regards,

Samruddhi

RE: Build Preset values change slash to backslash

Samruddhi Jadhav — Mon, 02 Mar 2026 10:19:43 GMT

Hi,

I can see that you are using an older NCS version which may be causing the issue. What are the other files in your boards folder? If you are using a custom board, I would recommend you to take a look at : nRF Connect SDK Intermediate Course - Board files

Best Regards,

Samruddhi

RE: Build Preset values change slash to backslash

Samruddhi Jadhav — Fri, 27 Feb 2026 14:42:43 GMT

Hi,

Thanks for providing the screenshots. I will look into this issue with the team and come to you with an update by early next week.

Best Regards,

Samruddhi

RE: Build Preset values change slash to backslash

SvenSi — Fri, 27 Feb 2026 04:38:55 GMT

The CMakePreset: looking correct

The Build-Configuration relying on the Preset: The Path contains Backslash = not OK

The Possible selections: Shown with Slash = OK

RE: Build Preset values change slash to backslash

Samruddhi Jadhav — Thu, 26 Feb 2026 08:18:17 GMT

Hi,

Can you please share a screenshot of this issue so that I can look more into this?

Best Regards,

Samruddhi

RE: Build Preset values change slash to backslash

SvenSi — Tue, 24 Feb 2026 10:25:27 GMT

I´m not sure if CMake is doing the conversion from CMakePreset.json to the buil-configuration. But I know, that it is changed in the wrong way.

I would like to find a solution that allows to use the CMakePreset.json like it should be. It is tedious and error-prone to have to manually correct the settings each time. This is especially true if another employee wants to work on this project later and may not know exactly what to do.

RE: Build Preset values change slash to backslash

Samruddhi Jadhav — Tue, 24 Feb 2026 10:11:10 GMT

Hi,

Presets are supposed to use /. The / is also preferred by the JSON format and CMake so the paths you are seeing in CMakePreset.json seem correct. Generally, Windows uses \ to save file paths. / is accepted by Windows in CMake but there are a few factors to note. The issue can be due to Windows OS as you mentioned because the IDE normally saves the paths using \. So, the VS Code extension itself uses path separators as per Windows but it does support / as well. I think that when you save the configurations, CMake may be changing to the correct format by itself when managing CMakePreset.json.

Let me know if you have any further questions.

Best Regards,

Samruddhi