Go rules example with third party package?
See original GitHub issueBuck for go is great, BUT, creating BUCK files manually for even the most common third party packages seems quite a hassle.
How could you use Buck (from the naive-developer point of view) with, say, golang.org/x/oauth2
?
Could you provide examples?
Issue Analytics
- State:
- Created 7 years ago
- Comments:6 (1 by maintainers)
Top Results From Across the Web
Using rules_go with go modules and generated packages
The experience of building go code with rules_go / gazelle works pretty well in general. Unfortunately when using both go modules for dependency ......
Read more >Third-party dependencies with go_module() - Please Build
Use go_module() to download and compile third party go modules; Download and compile the library and binary parts of a module separately; Resolving...
Read more >GoLang Packages and Modules | Beginners Go Tutorial
We will learn how importing packages work and how we can pull in third party libraries outside of our Go Path using modules....
Read more >Golang with Bazel - step by step tutorial - Medium
In this short write-up, we will go over how to use Golang with the Bazel build system. In particular, we will go over...
Read more >Go Modules Reference - The Go Programming Language
For example, the module "golang.org/x/net" contains a package in the directory ... If a module might be depended on by other modules, these...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I just wrote a simple tool to do this https://github.com/vmagro/go-buck-generator It’s a bit rough around the edges right now (see the TODO in the README) but it works for a lot of cases making the whole thing a lot less tedious
Any news on this? What do you exactly mean by TARGET files?
Slightly off-topic: I’m also still looking for a good way to manage my go dependencies in a buck project (outside a GOPATH), ideally without checking in all the vendored libraries. There’s a myriad of different go vendoring/dependency tools, but none seem to fit the bill. Pointers appreciated.