-
Notifications
You must be signed in to change notification settings - Fork 15.6k
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
Protobuf is unbuildable without --enable_runfiles
#19410
Comments
My understanding is that unfortunately Bazel support for Windows is not great at the moment. We have had a lot of problems with MSVC cl.exe not being able to handle file paths longer than 256 characters, and Bazel seems to like producing really long file paths. It's possible that that is related to this problem you ran into. We would be open to ideas on how to improve our Bazel setup for Windows, though. |
Yeah, windows support has been incredibly painful. I actually think this is a bug within Bazel and not necessarily protobuf, but it manifests the most with protobuf. My current thought is the behavior of |
I've hit another issue which appears to stem from
This is not the same issue as the command line being too long as the full path to this file would the following 198 characters:
Full command line:
|
Trying to compile protobuf with Bazel on windows machines that do not have runfiles enabled will lead to errors like the one linked below. I highly suspect the behavior is caused by the
_virtual_includes
directory being in a different form when runfiles are enabled vs when runfiles are not.What version of protobuf and what language are you using?
Version: v28.3
Language: C++/Java/Python/C#/Ruby/PHP/Objective-C/Javascript
What operating system (Linux, Windows, ...) and version?
Windows 10
What runtime / compiler are you using (e.g., python version or gcc version)
MSVC
What did you do?
Steps to reproduce the behavior:
bazel --nowindows_enable_symlinks build //:protobuf --noenable_runfiles
What did you expect to see
Successful builds.
What did you see instead?
The full command line command:
Make sure you include information that can help us debug (full error message, exception listing, stack trace, logs).
Anything else we should know about your project / environment
The text was updated successfully, but these errors were encountered: