Skip to content

Update bazel module setup#461

Merged
gchatelet merged 3 commits into
google:mainfrom
keith:ks/update-bazel-module-setup
Jun 25, 2026
Merged

Update bazel module setup#461
gchatelet merged 3 commits into
google:mainfrom
keith:ks/update-bazel-module-setup

Conversation

@keith

@keith keith commented Jun 24, 2026

Copy link
Copy Markdown
Contributor

Downstream in the bazel central registry there is some naive parsing
that doesn't work well with constants like this. We can inline this
value instead. I left around CPU_FEATURES_VERSION to make sure the sed
was unambiguous.

This also removes the repo_name which was unused

Downstream in the bazel central registry there is some naive parsing
that doesn't work well with constants like this. We can inline this
value instead. I left around CPU_FEATURES_VERSION to make sure the sed
was unambiguous.

This also removes the `repo_name` which was unused
@keith

keith commented Jun 24, 2026

Copy link
Copy Markdown
Contributor Author

an alternate common pattern we can do is just set this to version = "0" and let it be patched in the BCR. this number only matters when being resolved in that setting

@Mizux

Mizux commented Jun 24, 2026

Copy link
Copy Markdown
Collaborator

Got the same issue with or-tools, highs and few other modules I maintain on BCR, tooling don't support variable in version...

@Mizux

Mizux commented Jun 24, 2026

Copy link
Copy Markdown
Collaborator

an alternate common pattern we can do is just set this to version = "0" and let it be patched in the BCR. this number only matters when being resolved in that setting

need to provide an overlay or a patch (cumbersome in bcr ecosystem since compared to cmake fetchContent we don't easily have the orig repo cloned) so if we can have the correct version upstream will be better imho

Comment thread scripts/make_release.sh Outdated

@gchatelet gchatelet left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Oops good catch

@gchatelet gchatelet merged commit 044ec8c into google:main Jun 25, 2026
39 of 40 checks passed
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.

4 participants