Advice on switching toolchain with linux vscode extension?

[Spector]

I want change toolchains, so when i open nrfconnect terminal I can use my own west command.

I've read link, link and link

Option in the picture lets me install or open directory but not actually switch to build. I don't have the welcome home page, just a side bar. The >nrf connect ... welcome home page also toggles the side bar. The ctrl + p select version doesn't exist



I'm using linux and I wonder if the software is half baked.

I was able to create a application and build config, and (if it compiled) i somehow managed to update the repo but not the toolchain...then maybe after shut down and reopen i got the toolchain working...but it was horrible and i didn't feel i was able to revert from 2.6.1 back to 2.9.0.



I want the freestanding because i tend to use west_build.sh which will call stuff in. On a side note i didn't notice -DNCS_TOOLCHAIN_VERSION=2.6.1 / 2.9.0  do one lick of difference if the terminal was already started with certain setup.



Lastly when switching between shells if the env setting are somehow configured correctly then 


However I've been unable to find a reliable way to do this.

So in short how can i configure the shell so when i open the nRF Connect terminal it has the correct environment variables.

Regards,

Wes

[Vidar Berg]

Hi Wes,

I want change toolchains, so when i open nrfconnect terminal I can use my own west command.

I'm not sure I fully understand what you mean here, so please correct me if I'm wrong. Do you only want to change the toolchain version, or do you also have custom west commands in addition to those included in the SDK that you would like to use? Note that the west workspace you are in and the toolchain environment you have set are separate things.

If you have the project open in vs code, you can click the button shown below to open a terminal with the same toolchain as the active build configuration:

It is also possible to set the toolchain environment yourself outside of vs code by using nrfutil with the toolchain manager package installed:

$ source <(nrfutil toolchain-manager env --as-script --ncs-version=v2.7.0)

Best regards,

Vidar