Philipp Wagner
Philipp Wagner
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...
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 I run the following fusesoc command: ```sh fusesoc --cores-root /data/home/no56hud/src/optimsoc/examples run --target=lint --tool=spyglass optimsoc:examples:compute_tile_nexys4ddr --help ``` I get a help message like the one below: ``` usage: fusesoc run...
Currently fusesoc always outputs some error or warning messages. For some use cases, e.g. the new and fancy bash completion, it would be nice to have a way to be...
Currently, generators are only able to produce source files, which are then added to the file list. For advanced use cases, e.g. in OpenTitan, that's not enough. We currently are...
It would be nice to have a per-project config file for fusesoc which allows setting default options, like cores root and build directory. (1) Implementation idea: Extend the config file...
There's relatively new project, sv2v (https://github.com/zachjs/sv2v), which enables SystemVerilog to Verilog pre-processing. I'd like it to integrate into our flow for certain targets. Olof: what do you think would be...
Currently `capi2/core.py` throws many `SyntaxError`s without indicating the exact source location this error comes from. You can guess the file typically by enabling more verbose logging, but that's non-ideal nonetheless....
What can we do to simplify the pattern to run a given target? Users don't want to type "fusesoc run --target=lint", but "fusesoc lint" just like they call "fusesoc build"....