Add target_compatible_with parameter to proto_toolchain in Bazel rules #22429
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
In some cases, few targets can require different proto_toolchains.
github-actions
bot
removed
the
🅰️ safe for tests
shaod2
approved these changes
Jul 14, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In some cases, few targets can require different proto_toolchains.
In my case, my project defines different toolchains and each of them can define its own Protobuf compiler from its SDK, independent of the others. Restricting it with exec_compatible_with is not an option, since each target is built on the same x86_64 system.
I patched this Bazel file in my build system and thus was able to define the Protobuf compiler independently for each target.