testing new toolchain in vs code - issues?

RE: testing new toolchain in vs code - issues?

Priyanka — Wed, 20 Sep 2023 09:09:26 GMT

Hi Lorenzo,

I have heard back from the experts. The failed command might have been caused because of git not being installed in the system. We have a fix for this which should be reflected in the upcoming recovery release.

Also, they mentioned that commands for opening the SDK directory in a shell are not included, but the user can cd $ZEPHYR_BASE to get there (cd %ZEPHYR_BASE% on Windows).

Moreover, you do not have bash available in your environment because the system doesn't see one. Shell executables need to be configured under settings: terminal.integrated.profiles.windows when it's not in the PATH. They should appear as a terminal profile selector when there is more than one in the top-right corner of the TERMINAL panel.

Hope this helps. 🙂

Regards,

Priyanka

RE: testing new toolchain in vs code - issues?

Priyanka — Tue, 19 Sep 2023 08:54:47 GMT

Hi Lorenzo,

I was not able to reproduce you installation errors unfortunately. It installed successfully here at my end. I have asked internally regarding this and will check around for the "Open bash" functionality too and get back to you soon.

Regards,

Priyanka

RE: testing new toolchain in vs code - issues?

Lorenzo Amicucci — Mon, 18 Sep 2023 10:12:41 GMT

on powershell, It returns nothing.
Definitely, I agree something on the terminal is not set up right

RE: testing new toolchain in vs code - issues?

bstewart-cae — Fri, 15 Sep 2023 18:06:11 GMT

Looks like that terminal profile is not set up properly. if you type in

>echo $PATH

what pops up?