nRF Connect West Env Platform Specific Configuration

[M.Bynum]

I'm using the nRF Connect extension for VS Code and running into an issue with Sysbuild where calls to cmake for building the app image and the MCUboot image will use different python interpreters, there is discussion of this same problem on the zephyr-nix repo as well: https://github.com/nix-community/zephyr-nix/issues/48).

I've had success overcoming this issue by setting the PATH variable in the workspace setting...

"nrf-connect.west.env": {

"$base": "terminal",

"PATH":"${workspaceFolder}/.venv/bin:${env:PATH}"

},

However, this is not useful across the dev systems of my team as Posix & Windows have different PATH formats and priorities.

 

Is there another solution for making this bandaid cross platform compatible?

For reference, I am using zephyr-sdk-0.17.4 toolchain and west workspace has been setup with https://github.com/sdk-nrf v3.2.1.

My system is running latest MacOS, my colleagues are on latest Windows 11, our test environment is running pipelines in an Ubuntu 24.04 LTS based Docker image.

[Carl Richard]

Hello!

Thanks for reaching out. I need some more details about your development environment to be able to help you properly: have you manually installed the mentioned toolchain, or are you using the built in toolchain manager in the nRF Connect extension for VS Code? 

Best regards,
Carl Richard

[M.Bynum]

Hi Carl,

I manually installed the Zephyr SDK per here: https://docs.zephyrproject.org/latest/develop/toolchains/zephyr_sdk.html

The extension seems to pick it up with the addition to my settings.json of:

"terminal.integrated.env.osx": {

    "ZEPHYR_SDK_INSTALL_DIR":"/Users/<user>/tools/zephyr-sdk-0.17.4"

}

Correction on the above... adding the PATH variable into the nrf-connect.west.env setting still fails when trying to "build all configurations", while adding the PATH variable to terminal.integrated.env.osx is what allows for successful building in the terminal (west build -b <board> <app path> ...).

"terminal.integrated.env.osx": {

    "PATH": "${workspaceFolder}/.venv/bin:${env:PATH}",

},

Best regards,

Michael

[Carl Richard]

Hi again!

Thanks for the information. I think this issue could be avoided if you were using our recommended methods of installation, wither using the built in SDK and toolchain management in the nRF Connect SDK extension or using nRF Util. They setup the dev environment containerized. Could this be a viable solution for you?

I do understand that it may be more practical to have a global installation, like yours. If you want to continue using this, could this documentation on using the West environment on MacOS and Linux help?

Best regards,
Carl Richard