Closed HU90m closed 8 months ago
Maybe we can have all OSS tools that we rely on in this repo in the future? (e.g. verilator) If that's desirable, then perhaps we should keep each package in a separate file.
Maybe we can have all OSS tools that we rely on in this repo in the future? (e.g. verilator) If that's desirable, then perhaps we should keep each package in a separate file.
For standard tools like ventilator, I think we should depend on and contribute to upstream (nixpkgs). For packages with custom patches (like this one), I think we should add a flake.nix
to the repo holding the patch.
Maybe we can have all OSS tools that we rely on in this repo in the future? (e.g. verilator) If that's desirable, then perhaps we should keep each package in a separate file.
For standard tools like ventilator, I think we should depend on and contribute to upstream (nixpkgs). For packages with custom patches (like this one), I think we should add a
flake.nix
to the repo holding the patch.
Yes I agree. Since this repo stands alone, I think it makes sense to to stay specific to the RISCV toolchain packaging. We should probably use a different repo somewhere to keep useful overlays/patches etc to the upstream tools for our needs.
It would be nice to have two nix derivations in this repo, the one in this PR (which just pulls the github releases binary cache and patchelf's it) and another one which can build from source. I have some local changes but got bored testing it because the build is so slow.
For standard tools like ventilator
It do feel like that sometimes :rofl:
Updated to used the imcb
toolchain, so I can use the practice wizardry with bitmanip instructions
Since https://github.com/lowRISC/lowrisc-nix/pull/4, this isn't really needed. Would still be nice to have a nix based build of these one day.
Moving lowrisc-toolchain release download flake from https://github.com/lowRISC/ibex-demo-system here, so it can be used from other repos.