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
I don't know anything about go, never mind go get, but when I installed the latest version 1.18 inside WSL2, I was alerted to use go install instead of go get. So, what I ended up having to do to use this to pipe through windows:
GOOS=windows go install github.com/jstarks/npiperelay@latest
For future people who land here:
you'll want to check your GOPATH via
go env GOPATH
and then make sure that npiperelay.exe is in your GOBIN -- which might be something like /home/<USER>/go/bin/. I then ended up having to setup a symlink as so
Thanks for the info, for more details on the issue, I also just ran it in a new environment and I got this:
➜ local go get -d github.com/jstarks/npiperelay
go: go.mod file not found in current directory or any parent directory.
'go get' is no longer supported outside a module.
To build and install a command, use 'go install' with a version,
like 'go install example.com/cmd@latest'
For more information, see https://golang.org/doc/go-get-install-deprecation
or run 'go help get' or 'go help install'.
I don't know anything about
go
, never mindgo get
, but when I installed the latest version1.18
inside WSL2, I was alerted to usego install
instead ofgo get
. So, what I ended up having to do to use this to pipe through windows:For future people who land here:
you'll want to check your GOPATH via
and then make sure that
npiperelay.exe
is in yourGOBIN
-- which might be something like/home/<USER>/go/bin/
. I then ended up having to setup a symlink as sothere was no need to link this back to my windows user.
The text was updated successfully, but these errors were encountered: