-
Notifications
You must be signed in to change notification settings - Fork 87
can't find package in gopath #102
Comments
Do you have files like |
@stamblerre I finally stumbled upon this answer and I can say this is the issue my side, but I have no idea how to build these objects... How do we do so? EDIT Managed to do it by tanking the |
You should be able to build |
Having the same issue :/ |
@Vizualni: Do you have |
@laily123: Yes, |
I think this is related to #46. I think my issue was the same as yours:
I tried this both in and out of my GOPATH. I'm not sure what the module system has done to my work set up, but things have been messed up for sure, and this made VS Code no more useful than an auto-formatter. |
@sethgrid: For modules support, you should use stamblerre/gocode. mdempsky/gocode does not support modules. VSCode downloads both and renames the stamblerre/gocode binary to gocode-gomod, so both versions can coexist. |
@stamblerre |
@stamblerre yes,this problem is loss .a file. go install this project genrate .a flie is the correct solution to this problem |
is that means, every time I change my package, I have to install it ? |
this is gocode -s -debug output
I am pretty sure that the paths to these packages are in my gopath. only find system built-in packages like fmt and time
vscode version
The text was updated successfully, but these errors were encountered: