How does nRF Connect for VS Code determine the shell for default "Build" and "Flash" tasks?

RE: How does nRF Connect for VS Code determine the shell for default "Build" and "Flash" tasks?

Marte Myrvold — Wed, 26 Apr 2023 07:41:35 GMT

Hi,

Can you try starting VS Code from within the environment where all PATHs are set to your wanted toolchain? This should help VS Code inherit the same environment.

Best regards,
Marte

RE: How does nRF Connect for VS Code determine the shell for default "Build" and "Flash" tasks?

stvnwn — Mon, 24 Apr 2023 15:57:37 GMT

I tried setting the $PATH environment variable in .bashrc, as well as in "nrf-connect.west.env" from settings.json. Running the "Build" task from the Actions View still fails after performing either procedure with an error message:

/bin/sh: west: command not found

I initially thought that nRF Connect for VS Code would, by default, use my default shell on my macOS computer, which is /bin/zsh. It does for the nRF Connect terminal profile, but not for tasks in the Actions View (seems that they default to /bin/sh). Is there a way to change the shell for tasks in the Actions View?

RE: How does nRF Connect for VS Code determine the shell for default "Build" and "Flash" tasks?

Marte Myrvold — Mon, 24 Apr 2023 11:41:54 GMT

Hi,

The nRF Connect for VS Code extension queries Bash for its environment by executing the ~/.bashrc file. Adding the path of west and other dependencies to ~./basrc should solve the issue. See West environment on macOS and Linux for more information.

You can also add environment variables to nrf-connect.west.env, so another solution is to set paths and environment variables not picked up by the extension in nrf-connect.west.env. See our documentation about this here: nrf-connect.west.env.

"nrf-connect.west.env": {
    "$base": "terminal",
    "CUSTOM_ENV_VAR": "custom value",
    "OTHER_ENV_VAR": "another value",
}

Best regards,
Marte