I suspect that the number of Bazel experts out there is not terribly large, but: I'm hitting github.com/bazelbuild/rul… - one of the dependencies of a go_library() target needs a specific build tag to work in my environment. Is there any way to do that at the moment?
Ok so the right thing to do here is to express the tags in the go_binary() target, but what's actually breaking things for me here is that go_repository() has "helpfully" called gazelle and generated a BUILD file that has copts set for the default tags
Which means even when I pass the correct build tags, gcc is being called with the flags set by the wrong build tags, and all the #ifdefs are wrong as a result
Ah ok the fix is to add build_tags = ["foo","bar"] to the go_repository() definition in the workspace config
• • •
Missing some Tweet in this thread? You can try to
force a refresh
