fusesoc
fusesoc copied to clipboard
olofk
Package manager and build abstraction tool for FPGA/ASIC development
Please add a mechanism to specify a branch/tag name and additional options like '--depth' to a library's git URI. For repositories that are large, with many branches and tags, without...
I'm wondering what the best practice is for dealing with the restriction that only dependencies' default target can be used. If I have multiple tool- and flag-based configurations that I...
This is a follow-up to #391. With the code in #391, generators are run only once during the build process, and not again if new dependencies show up as result...
Hi Is it possible to have fusesoc check-out remote cores without landing up with multiple copies of the same repository and version ? Currently, fusesoc checks out a repository for...
As mentioned e.g. in https://github.com/olofk/fusesoc/issues/425, when two targets are being run on the same core, the latter will overwrite the source directory of the former. This was done in a...
This behavior results from 2 facts: 1. When sources are exported, they are copied to the `src/` directory which is located in the `build/core/` directory, not in the `build/core/target/` directory....
I'd like to use a generator to build our toplevel file. We have the following setup: - Each register-mapped IP core comes with a small config file describing its register...
Since d8ece6b5 file names in filesets can contain environment variables, which are expanded during parsing. I'd like to better understand the use case for this feature, and potentially get rid...
When fusesoc run is called with a non-existing target, it will report that it couldn't find the correct tool instead of saying that the target doesn't exist. Bonus point for...
The idea is to plot a dependency graph for the given core/system
