Skip to content
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

Add a dependency for rules_cc to MODULE.bazel #56

Merged
merged 1 commit into from
Sep 17, 2023

Conversation

rrbutani
Copy link
Contributor

rules_perl requires the rules_cc repository to be present: https://github.com/bazelbuild/rules_perl/blob/022b8daf2bb4836ac7a50e4a1d8ea056a3e1e403/perl/perl.bzl#L19

While this isn't an issue when running the examples for this repo (i.e. bazel build --enable_bzlmod //examples/hello_world:hello_world works fine — rules_cc appears to be implicitly added to the repo mapping for the current root module's repo), when depending on rules_perl from another module this becomes an issue.

Even if the dependent pulls in the rules_cc module, rules_cc will not be visible in rules_perl's mapping unless rules_perl also declares a dependency on it.

`rules_perl` requires the `rules_cc` repository to be present:
https://github.com/bazelbuild/rules_perl/blob/022b8daf2bb4836ac7a50e4a1d8ea056a3e1e403/perl/perl.bzl#L19

While this isn't an issue when running the examples for this repo
(i.e. `bazel build --enable_bzlmod //examples/hello_world:hello_world`
works fine — rules_cc appears to be implicitly added to the repo mapping
for the current root module's repo), when depending on `rules_perl` from
another module this becomes an issue. Even if the dependent pulls in the
`rules_cc` module, `rules_cc` will not be visible in `rules_perl`'s mapping
unless `rules_perl` also declares a dependency on it.
@skeletonkey skeletonkey merged commit 366b6aa into bazel-contrib:main Sep 17, 2023
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.

2 participants