-
Notifications
You must be signed in to change notification settings - Fork 387
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Gazelle not including pregenerated .syso files despite rules_go support #1999
Comments
The patch below solves the problem above, but I'm not sure how generalizable it is. Perhaps a start to further discussion.
|
This looks reasonable to me, thanks for working it out. Could you send it as a PR so that we can properly discuss it? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What version of gazelle are you using?
0.37
What version of rules_go are you using?
47.1
What version of Bazel are you using?
7.4.1
Does this issue reproduce with the latest releases of all the above?
Some issues because of bzlmod migration, I don't think it's related. Will keep trying. Getting errors with platforms dep conflict between proto and rules_go (I think?) in a WORKSPACE repo after 0.37.
What operating system and processor architecture are you using?
Linux amd64
What did you do?
Use gazelle to import and generate BUILD files for https://pkg.go.dev/gioui.org, including https://pkg.go.dev/gioui.org/shader
What did you expect to see?
Autogenerated gazelle rules would include pregenerated
.syso
build files from upstream in the go_library rules as bazel-contrib/rules_go#4148 was merged. However, these files are not automatically included, so various symbols are undefined, output below. I think this is the right place to file this issue, please advise if it is not. Thanks!What did you see instead?
The text was updated successfully, but these errors were encountered: