You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 15, 2023. It is now read-only.
We should still make some changes to avoid the confusion. Here is what I propose:
If go.toolsGopath setting is set, then the process that installs the tools should unset the GOBIN env variable, so that the tools get installed in the right place
GOBIN should be added to the list of places where the extension looks for the tools.
ramya-rao-a
changed the title
Tools build ("Successfully"), but don't appear in the tools directory.
Tools build ("Successfully"), but don't appear in the tools directory when GOBIN is set
Nov 21, 2018
I'm trying vscode for the first time, and I had the same problem. I've got GOBIN set to ~/.local/gobin, so Go installs all compiled binaries in that path by default. Vscode installs the binaries successfully there too, but when reloading or restarting the editor, it complains it can't find the binaries it just installed: Analysis Tools Missing. I'm not sure vscode-go even uses GOBIN anywhere in the code, so it looks in the wrong place for the installed binaries.
I've solved the problem by manually setting go.toolsGopath.
Ideally, vscode would respect the GOBIN environment variable when one is set by the user, to avoid a mismatch between Go's and vscode's idea of where the binaries are stored.
But, when I look at the contents of
/Users/ronb/gotools/bin
:So, of course, anything that depends upon tools fails and tells me I need to install them.
This is VSCode 1.29.0 on High Sierra 10.13.6.
The text was updated successfully, but these errors were encountered: