Potential out-of-date instruction when working with [vscode-hello-go]
Describe the bug Potential out-of-date instruction when working with vscode-hello-go. Step "Press F5 to download the program and run it" doesn't work.
Getting error:
- No files selected for download.
- go -o hello flag provided but not defined: -o
To Reproduce Steps to reproduce the behavior: Following the steps described here.
Expected behavior It should be able to upload to EV3 and execute the demo program successfully.
Screenshots
https://github.com/user-attachments/assets/46915b83-39cb-4192-b8c2-f368d9e505c9
Desktop (please complete the following information):
- MacOs Sonoma Version 14.6.1
- Vs code: 1.95.3
- Go: go1.23.3 darwin/arm64
- EV3DEV: ev3dev-stretch
- EV3 wifi connection mode, can successfully ssh and connect with vscode-ev3dev-browser
PS: I am a GO learner, I made sure my current VS code setup can run go successfully, like this one.
Files under .vscode are unchanged, eg: using default launch.json and settings.json.
Additional context
I recently came across this fascinating extension project. The functionality enabling EV3 owners to code, run, and debug in a live IDE environment is truly exciting.
I understand that neither vscode-hello-go nor this project is under active development, but I’m eager to test it out nonetheless.
My current suspicions are: 1. The Go version might not be supported. 2. VS code security setting.
Any assistance or guidance would be greatly appreciated 🙏!
Does it work if you change the command to go build -o hello?
Does it work if you change the command to
go build -o hello?
It works now and successfully got complied:
However the F5 press to deploy still ends up error:
* Executing task: go -o hello
flag provided but not defined: -o
Go is a tool for managing Go source code.
Did you run the command manually or did you modify .vscode/tasks.json?
Did you run the command manually or did you modify
.vscode/tasks.json?
I ran the command manually.
After your comment, I also tried editing the original .vscode/tasks.json to below:
"args": [
"build", "-o", "hello"
]
Which fixed the compiling issue, should I create a PR to apply this?
However the uploading to ev3 part is still not working, despite I updated launch.json to an existing folder already:
I don't think you should change ${workspaceFolderBasename} to test2. I don't see any folder with that name, so not surprising that it says it doesn't exist.
I don't think you should change
${workspaceFolderBasename}totest2. I don't see any folder with that name, so not surprising that it says it doesn't exist.
My understanding is this file path is the ev3 file path where we want to upload the program to. Is that not?
If I leave it unchanged, keep using ${workspaceFolderBasename}, it also doesn't work.