-
-
Notifications
You must be signed in to change notification settings - Fork 219
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
Move minimum supported version to Bazel 7.0.0 #229
Conversation
Note that I removed I would add this flag to llvm but it's a bit more work that I really wanted to put into it since the difference isn't really important |
Thanks @keith. I will merge this when our minimum supported version becomes 6.4.0. |
Could we maybe add a check for the Bazel version and merge this fix? Thanks 😄 |
bump. this is affecting us too. |
1c6e45c
to
f570530
Compare
This removes the need to provide `--features=-libtool` on macOS.
* Drop `-fuse-ld=lld`. * Pin `toolchains_llvm` to bazel-contrib/toolchains_llvm#229. * Manually specify clang 17.0.6 files (required by the above).
* Add LLVM/Clang via foreign_rules at version 17.0.6. * Fix clang-format detection for the external repo. * Support version 19 in auto-detection. * No bzlmod. * Add foreign_rules_cc. * Add 3rd config to CI (GCC). * Show clang-format binary on failure * Working combination: * Drop `-fuse-ld=lld`. * Pin `toolchains_llvm` to bazel-contrib/toolchains_llvm#229. * Manually specify clang 17.0.6 files (required by the above).
This removes the need to provide flags like:
--incompatible_enable_cc_toolchain_resolution
--features=-libtool
on macOS.--features=-supports_dynamic_linker
on macOS.As part of the update, test dep versions have also been updated.