raspberrypi / pico-vscode

The official VS Code extension for Raspberry Pi Pico development. It includes several features to simplify project creation and deployment.
https://marketplace.visualstudio.com/items?itemName=raspberry-pi.raspberry-pi-pico
Mozilla Public License 2.0
131 stars 16 forks source link

Failed to setup example. #25

Closed SeyranGrig closed 4 months ago

SeyranGrig commented 4 months ago

Failed to setup example error when create new project from examples

SeyranGrig commented 4 months ago

my version Beta 14 (RC 1)

will-v-pi commented 4 months ago

Which example was this with? Additionally, what platform were you using (Windows, MacOS, Linux, etc)?

SeyranGrig commented 4 months ago

I try on Windows any examples

SeyranGrig commented 4 months ago

is it possible that the reason is that I have the Pico SDK v1.5.1 installed

SeyranGrig commented 4 months ago

I remove installed Pico SDK v1.5.1, and i create project from example without errors

Kabron287 commented 4 months ago

Windows10 x64 v0.14.0 (pre-release) No separate SDK installation.

Failed to setup example

gokhan-bektas commented 3 months ago

Same here. Win 10 x64 VSCode 1.91.1 Raspberry Pi Pico Extension v0.14.0 (pre-release)

Tested with and without Windows Pico SDK installer installed. Manually cloned examples to c:\users\myself.pico-sdk\examples and to c:\users\myself.pico-sdk\sdk\1.5.1\examples

Purged the VScode, all extension folders, all registry entries and re-installed. It is still the same.

Tried using 1.5.0, didn't make a difference.

Also tried to see if it is looking for a different folder: image

will-v-pi commented 3 months ago

Thanks, I've found the bug - there's some missing quotes, causing the space in the git path (Program Files...) to cause a command failure. You can download the latest .vsix build from the actions artifacts here, and the fix will also be included in the next release

@gokhan-bektas As you've manually edited stuff in the .pico-sdk directory, I'd recommend deleting that whole directory to make sure everything is installed correctly, and then trying again with the updated extension