Skip to content

Conversation

mmorel-35
Copy link

@mmorel-35 mmorel-35 commented Aug 26, 2025

Description

This updates bazel to 7.6.1 and migrate to bzlmod

Closes #187

@mmorel-35 mmorel-35 marked this pull request as ready for review August 26, 2025 17:13
…management

Signed-off-by: Matthieu MOREL <matthieu.morel35@gmail.com>
@@ -7,3 +7,5 @@
# enables improved Bazel C++ toolchain resolution method that became the
# default in newer Bazel version and does not cause problems, we keep it.
build --incompatible_enable_cc_toolchain_resolution
# Enable Bzlmod for every Bazel command
common --enable_bzlmod
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks great to me, thanks for the PR!

Pardon my ignorance, one question: please confirm this setting isn't contagious and that the change is compatible with non-bzlmod projects. What I mean is: projects like Envoy can still depend on cpp-sdk without immediately enabling bzlmod?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The .bazelrc only impact the current project not those depending on it.
Having MODULE.bazel and WORKSPACE allow to support both modes during the migration.

I'm actually trying to migrate envoy to bzlmod but the more dependencies are still using WORKSPACE, the harder it is , see envoyproxy/envoy#40692

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

bzlmod support
2 participants