Philipp Wagner
Philipp Wagner
Many EDA tools support digesting file lists in *.f files. Having a (pseudo-)backend which generates these files would serve as stopgap for EDA tools which we don't support natively so...
edalize describes backend options as part of the backend class. This information is used to generate backend documentation in FuseSoC's documentation. However, for edalize's own documentation, we have a hardcoded...
If no device is connected, we get this error message. We should tidy it up to be more helpful and less of a stacktrace. ``` vivado -quiet -nolog -notrace -mode...
We need support for Synopsys Design Compiler for synthesis. This will most likely be a rather minimal backend, where only the filelist is coming from edalize, all other configuration is...
Original request: Make parameters (e.g. vlogdefine/vlogparam) available as use flag, to be able to do something like `depend: vlogdefine_SYNTHESIS ? corp:lib:synthesislib`. EDIT: Making flags available as parameters is easier and...
The documentation at https://fusesoc.readthedocs.io/en/master/user/overview.html#core-search-order doesn't mention the FUSESOC_CORES environment variable, or how it relates to the search order.
Generators can be useful to transform configuration files or templates into code. To ensure that fusesoc can fully track dependencies (and rebuild only if sources change) [1] we need to...
Currently, generated cores (i.e. core files written by a `generator`) are inserted into the list of cores, but their dependencies are ignored. After this commit, cores are inserted into the...
The tools section is mentioned as not inherited in https://fusesoc.readthedocs.io/en/latest/user/build_system/dependencies.html#what-happens-if-a-dependency-is-specified which is wrong. Also double-check the other sections and maybe add a test?
FuseSoC handles a lot of file paths, currently as strings. That's often confusing and can lead to bugs, e.g. when describing paths on Windows. Additionally, manipulating paths as strings requires...