nRF Connect for VS Code Preset save broken when building on a different drive on Windows

[Rait]

OS: Windows

Name: nRF Connect for VS Code
Version: 2023.11.301

Found an issue with saving the preset file (Save configuration as preset) when project is located on a different drive than VSCode.

Saving the preset:

When location is "C:/..." the CMakePresets.json has correct value. 

"CONF_FILE": "${sourceDir}/prj.conf"

When location is "E:/...":

"CONF_FILE": "$env{ZEPHYR_BASE}/e:/VCTest/hello/prj.conf"

[Rait]

It seems there is also something off with importing custom definitions from the CMakePresets.json (Add build configuration and select preset) when project is located on a different drive.

On C drive behaviour is correct:

On E drive:

CMake configure command also gets the incorrect value:

-DMY_VAR=C:/Users/Rait/AppData/Local/Programs/Microsoft VS Code/Value

[Naeem Maroof]

This is because VS Code extension is using address with reference.

I have saved the preset file and can see the same:

"CONF_FILE": "$env{ZEPHYR_BASE}/h:/ztemp/blinky_casepreset/prj.conf"

I can use the same preset file to build the configuration successfully

[Rait]

Correct. It does build, however absolute paths don't belong in source control. Issue can be worked around by manually modifying the CMakePresets.json.

However, there doesn't seem to be any workaround for the second issue.

[Rait]

Hi. Any updates on this?

[Maria Gilje]

Hello,

Sorry about the delay.

Rait said:

However, there doesn't seem to be any workaround for the second issue.

Please update your extension to the latest version and let me know if the issue persists. I have seen reports that a similar issue was resolved by updating to v2024.2.214.

Best regards,

Maria