pybind / pybind/pybind11_protobuf
Create a release package to enable adding pybind11_protobuf to Bazel Central Registry
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 67
- Forks
- 37
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
Could you please add a complete set of instructions on how to include and use with Bazel?
I added the following stanza to my WORKSPACE file:
git_repository(
name = "pybind11_protobuf",
branch = "main",
remote = "https://github.com/pybind/pybind11_protobuf.git",
strip_prefix = "pybind11_protobuf",
)
However, I cannot get the requirement for a com_google_protobuf dependency to work.
I believe the current practice would be to add this dep to MODULE.bazel:
https://registry.bazel.build/modules/protobuf/21.7
and then add this to the BUILD rule:
"@protobuf//:protos_python",
This however gives me this error:
no such package '@com_google_protobuf//': The repository '@com_google_protobuf' could not be resolved: Repository '@com_google_protobuf' is not defined and referenced by '@pybind11_protobuf//:native_proto_caster'
What's the correct way to get this to work?
(for future compatibility, I have filed a BCR request here https://github.com/bazelbuild/bazel-central-registry/issues/1121 )
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the current WORKSPACE stanza, the MODULE.bazel dependency configuration, and the BUILD rule referencing @com_google_protobuf. Compare those requirements with the linked Bazel Central Registry request. Done means a release package can be added to the BCR and the repository includes complete, working instructions for using it with Bazel.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100