-
Notifications
You must be signed in to change notification settings - Fork 424
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
Fixes build for Windows #1230
Fixes build for Windows #1230
Conversation
Not as simple as I thought.. |
- Removed C++ options in .bazelrc since we by default using Bazel 7 which defauts to c++17 - Shorten the workspace name to avoid long path issue on Windows. Fixes #1210
b08ae8d
to
07ff080
Compare
Turns out it's a long path issue on Windows. |
After this one, we still need to update rules_go to fix downstream breakage: https://buildkite.com/bazel/bazel-at-head-plus-downstream/builds/3592#018d0add-494c-4c59-b452-da6cd582688c |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
@vladmos Can you please try to update rules_go to fix the breakage with Bazel@HEAD?
|
@meteorcloudy Updated in #1234 |
* Fixes buildtools on Windows - Removed C++ options in .bazelrc since we by default using Bazel 7 which defauts to c++17 - Shorten the workspace name to avoid long path issue on Windows. Fixes bazelbuild#1210 * Fix test
Fixes #1210