mmicko
commented
2 years ago First would like to thank you for kind words. Also I am very glad that CHIPS Alliance is using OSS CAD Suite builds for development workflows. Agree that naming is a bit problematic in this case, but tgz name was actual scheme we used for our internal builds.
Change in code is quite trivial, but would like to check with other team members if there are some objections or use cases where this could break someones flow. Will rise this question to the rest of the team tomorrow.
To make things easy on your side I would suggest using https://github.com/YosysHQ/setup-oss-cad-suite in your workflows instead. That way you have just one date parameter to setup exact version (and this will work with any past or future version, even if we change naming scheme). 2nd example from https://github.com/YosysHQ/setup-oss-cad-suite/blob/master/README.md#usage is thing you need.
ekiwi
First of all I wanted to say that I love this project. This is the easiest way to get
yosys,verilatorand all the formal engines for use in CI. We are making use of this in the firrtl CI as well as the chisel CI. Since everything is hosted on github, the installation is blazingly fast.The one feature that would improve our experience is if we could easily define the version of the oss cad suite that we want to use as an environment variable (or github action variable). The problem here is that the release date appears in two different formats in the URL. If you could adjust the naming scheme of the archive somehow to match the git tag, that would make changing the release with a single variable a lot easier:
With this change we can use a shell variable like this to download the release: