Making the OpenTitan repository usable as a bazel dependency
Nobody has claimed this yet.
- Dominant language
- SystemVerilog
- Stars
- 3.6k
- Forks
- 1.1k
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 141
Description
This issue tracks all the problems that currently make the repository unusable (or partially so) as a bazel dependency. To be clear, the goal is to be able to do:
bazel_dep(name = "lowrisc_opentitan")
# + something related to overrides/bazelrc
and it should just work.
Overrides
Bazel overrides are currently specificed in the MODULE.bazel file, therefore ignored when not the root repository. One idea would be to create our custom bazel registry and let downstream users point to it so that they can get exactly the same patches/overrides. There is a WIP PR but it is not finished.
Contributor guide
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 MODULE.bazel and the WIP PR #27404, which explores how overrides are handled outside the root repository. Define the registry or overrides/bazelrc approach needed so a downstream project can use bazel_dep(name = "lowrisc_opentitan") successfully; done means the repository works as a Bazel dependency.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100