We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
bazel build //...
Output
PS C:\Users\SB\bazel_or-tools> bazel build //... INFO: Analyzed 2 targets (108 packages loaded, 3679 targets configured). ERROR: C:/users/sb/_bazel_sb/txbbv6pc/external/com_google_protobuf/src/google/protobuf/compiler/BUILD.bazel:97:11: Compiling src/google/protobuf/compiler/command_line_interface.cc [for tool] failed: (Exit 2): cl.exe failed: error executing CppCompile command (from target @@com_google_protobuf//src/google/protobuf/compiler:command_line_interface) C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.39.33519\bin\HostX64\x64\cl.exe ... (remaining 1 argument skipped) external/com_google_protobuf/src/google/protobuf/compiler/command_line_interface.cc(12): fatal error C1083: Cannot open include file: 'google/protobuf/compiler/command_line_interface.h': No such file or directory Use --verbose_failures to see the command lines of failed build steps. INFO: Elapsed time: 14.560s, Critical Path: 8.25s
Bazel installation on Windows was per
https://bazel.build/install/windows https://bazel.build/configure/windows
It has both VS Community Edition and clang
The text was updated successfully, but these errors were encountered:
Bazel generate paths for Protobuf way too long on windows...
Sorry, something went wrong.
now also tracked in:
Mizux
No branches or pull requests
Output
Bazel installation on Windows was per
It has both VS Community Edition and clang
The text was updated successfully, but these errors were encountered: