nRF connect VC Code, enable command line use

RE: nRF connect VC Code, enable command line use

y009 — Tue, 28 Mar 2023 11:13:58 GMT

Duh, when you said open from nrf connect, i just used the open vs code button.
Opening a terminal then using that to open vscode, does indeed work.

Thanks

RE: nRF connect VC Code, enable command line use

Vidar Berg — Tue, 28 Mar 2023 10:31:09 GMT

I do not see how this would not work for you. Did you do the same as outlined in the steps below?

1. Open command prompt from the Toolchain manager app

2. From the command prompt, open VS code by running 'code .' (Note: 'code.exe' must be in PATH for this to work)

3. Verify that the env. variables have been inherited in the VS code terminal by echoing the ZEPHYR BASE variable

RE: nRF connect VC Code, enable command line use

y009 — Tue, 28 Mar 2023 08:26:11 GMT

Doesn't seem to change anything.

Though it did give me a hint - the settings page in vscode.
The "nrf-connect....." variables as far as i understand control these, and I'd need to get them working outside of the nrf-connect extensions scope.

RE: nRF connect VC Code, enable command line use

Vidar Berg — Tue, 28 Mar 2023 06:50:37 GMT

The env. variables are exported if you open the terminal via the toolchain manager app. Have you tried that?

RE: nRF connect VC Code, enable command line use

y009 — Tue, 28 Mar 2023 06:37:07 GMT

Thanks but, sadly doesnt work for me, since the commands arent added to path by by default, at least with the latest nrf connect version on windows.

Hoping there are some commands from previous version i could utilize to get the same functionality

RE: nRF connect VC Code, enable command line use

Vidar Berg — Thu, 23 Mar 2023 08:53:14 GMT

Hi,

There are probably other ways to do this, but my workflow involves opening VS code from the terminal with 'code .'. This makes terminal in VS code inherit the env. variables (ZEPHYR_BASE, etc) from the terminal it was opened from.

Best regards,

Vidar