-
Notifications
You must be signed in to change notification settings - Fork 10
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
Disabling warnings from external headers #46
Comments
This useful feature was added to the default Bazel C++ toolchain in Bazel 5.0; see bazelbuild/bazel#13107. Fixes bazelembedded#46
This useful feature was added to the default Bazel C++ toolchain in Bazel 5.0; see bazelbuild/bazel#13107. Fixes bazelembedded#46
This useful feature was added to the default Bazel C++ toolchain in Bazel 5.0; see bazelbuild/bazel#13107. Fixes bazelembedded#46
I used to think this would be quite easy: tpudlik@80677f3 But to my surprise, this leads to errors when I try to compile Pigweed. Typical error:
I think what's going on here is that the This can probably be fixed by ensuring the include order for sysroot libraries is correct (so that they're overriden anyway), but the details are hazy to me. |
Yeah, I don't really have a good understanding of this either. I'm more than happy to change the usage of include flags in rules_cc_toolchain. I'll admit I'm not super familiar with the differences between; -I, -isystem, -iquote. I've read the docs for these flags, but I didn't feel like I fully understood the specific differences in enough detail to offer any guidance. |
The default Bazel C++ toolchain has a cool feature that allows disabling warnings from external headers: bazelbuild/bazel#13107. It would be nice to add this to rules_cc_toolchain, too. It would make clang version upgrades less painful for downstream users like Pigweed (since third-party deps may pick up lots of new warnings on a version upgrade).
The implementation in the default toolchain is actually very simple, but it's not possible to express as a
cc_feature
, so it's not immediately clear to me how to add it.Perhaps this should wait until the modular cc toolchains is finalized, since that may involve big changes to rules_cc_toolchain.
The text was updated successfully, but these errors were encountered: