-
Notifications
You must be signed in to change notification settings - Fork 687
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
Issue building with Bazel #1759
Comments
Big thanks to @chadxz for looking into this with me, we have some progress. I believe Gazelle is ignoring the The idea being that if the proto file is available, Gazelle should rely on building the library from the included .proto file. I'm still researching how to narrow down what is confusing it from there. |
I noticed that the code generator for the checked-in .pb.go file was different than the one used by Bazel. After setting a couple Gazelle directives, I got this closer:
Error changed to:
This seems like progress, but I'm not familiar enough with Bleve's build process to know if it is or not. |
@chadxz figured out we can disable protobuf for just this dependency and it works. However, I still think there's a fundamental issue with the protobuf configuration of this library, given that it requires overrides. Here's the workaround for anyone else that runs across this while this issue is open. Add Bleve to your
|
Associated
rules_go
issue here: bazel-contrib/rules_go#3357I added Bleve to our application dependencies and Bazel can no longer complete its build process. It appears that there is something different in the layout/configuration of Bleve that triggers this, as all my other dependencies build with Bazel with no adjustments. Repro repository here: https://github.com/kylekurz/bleve-issue-example
The text was updated successfully, but these errors were encountered: