Skip to content
This repository has been archived by the owner on Jul 15, 2023. It is now read-only.

gb support #249

Closed
anidotnet opened this issue Mar 17, 2016 · 3 comments
Closed

gb support #249

anidotnet opened this issue Mar 17, 2016 · 3 comments

Comments

@anidotnet
Copy link

This extension is great for go development, but it would be better if we have built in support for gb tool. Recently more and more projects are using gb for building and vendor management. Can we expect the same for near future?

@c3mb0
Copy link

c3mb0 commented Mar 23, 2016

If you go to File -> Preferences -> Workplace Settings, you can override the GOPATH for the current project. Thus, you can configure your GOPATH on a project basis. A typical gb project is as follows:

/myGbProject
  /src
  /vendor
    /src

If you set your GOPATH to "/full/path/to/myGbProject:/full/path/to/myGbProject/vendor" and reload VS Code, everything starts working swimmingly. :)

PS: Don't use tilde in the path.

@lukehoban
Copy link
Contributor

Thanks @c3mb0. I don't use Gb myself, but that definitely sounds like it should work.

Note also that as of #261, which was merged today, you can configure this even more simply in your .vscode/settings.json in your myGbProject folder:

{
  "go.gopath": "${workspaceRoot}:${workspaceRoot}/vendor"
}

@anidotnet Please reopen if you see problems even after configuring your per-project GOPATH.

@ghost
Copy link

ghost commented Jan 18, 2017

@lukehoban How does one specify to build with the gb tool instead of the standard go build?

@vscodebot vscodebot bot locked and limited conversation to collaborators Jan 24, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants