-
Notifications
You must be signed in to change notification settings - Fork 179
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
Don't load cc toolchain from rules_cc #779
Conversation
The cc toolchain autoconfig is out of sync from Bazel and doesn't work with VS2022. Related: bazelbuild/continuous-integration#1770
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.
examples/rich_structure/WORKSPACE needs the same change.
But the centos build fails now. with
| gcc: error: unrecognized command line option '-std=c++14'
Did rules CC change in a way to believe it is always above 14?
Yes, with Bazel@HEAD, we already switch the default C++ standard to 14: bazelbuild/bazel#18280 We should switch to use centos7_java11_devtoolset10 or just drop this platform. |
|
Got it, added in back in |
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 Yun!
The cc toolchain autoconfig in rules_cc is out of sync from Bazel and doesn't work with VS2022.
Related: bazelbuild/continuous-integration#1770