Skip to content

Add support for arbitrary Verilator versions#17

Open
MrAMS wants to merge 1 commit intokkiningh:masterfrom
MrAMS:master
Open

Add support for arbitrary Verilator versions#17
MrAMS wants to merge 1 commit intokkiningh:masterfrom
MrAMS:master

Conversation

@MrAMS
Copy link

@MrAMS MrAMS commented Dec 14, 2025

  • Allow specifying any Verilator version without pre-defining in VERSION_INFO
  • Add optional sha256 parameter for build reproducibility
  • Dynamically generate toolchain definitions per version

This enables users to use any Verilator release without modifying rules_verilator source code.

Example usage:

rules_verilator_toolchains(
    version = "5.020",
    sha256 = "9c9cfb72e075b0f73e83f1649e7d39dcb8368d19f31c3dc2cc31fa26c6ac1889",
)

- Allow specifying any Verilator version without pre-defining in VERSION_INFO
- Add optional sha256 parameter for build reproducibility
- Dynamically generate toolchain definitions per version

This enables users to use any Verilator release without modifying
rules_verilator source code.

Example usage:
  rules_verilator_toolchains(
      version = "5.020",
      sha256 = "9c9cfb72e075b0f73e83f1649e7d39dcb8368d19f31c3dc2cc31fa26c6ac1889",
  )
@MrAMS MrAMS mentioned this pull request Dec 14, 2025
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.

1 participant

Comments