[bazel] Re-examine the structure of `opentitan_binary`
Open
Nobody has claimed this yet.
Earlgrey-PROD Triaged
Priority:P2
SW:Build System
Type:Task
- Dominant language
- SystemVerilog
- Stars
- 3.6k
- Forks
- 1.1k
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 141
Description
Re-examine the structure of `opentitan_binary`.
- Consider whether a single rule should emit binaries for multiple exec_envs.
- Consider whether a macro should expand to a single-binary rules per exec_env.
- Work out implications for naming convention.
- Work out implications of the current practice of emitting multiple providers.
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 locating the definition and current uses of `opentitan_binary`, then compare how it handles multiple `exec_envs` and emits providers. Evaluate the single-rule and per-environment macro options, including naming conventions. Done means the structure, naming, and provider implications have an agreed resolution.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100