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

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"
Parents
  • 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

Reply
  • 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

Children
No Data
Related