Philipp Wagner

Reduce boilerplate in CAPI2 files

2

Currently we have a lot of small(ish) core files for our modules, all of which contain ``` targets: default: filesets: - files_rtl ``` Can we reduce the boilerplate a bit...

Windows: mixed directory separators in fusesoc init

1

I get the following output in CI: ``` fusesoc init -y INFO: Writing configuration file to 'C:\Users\appveyor\.config\fusesoc\fusesoc.conf' INFO: Initializing orpsoc-cores INFO: Cloning library into C:\Users\appveyor\.local/share\fusesoc\orpsoc-cores Cloning into 'C:\Users\appveyor\.local/share\fusesoc\orpsoc-cores'... INFO: Initializing...

Support for compiling and running cocotb simulations

1

Cocotb is, at its core, a VPI/VHPI/FLI library. This library is loaded by the simulator during startup. The behavior of this library (and therefore, cocotb) is influenced by a series...

CAPI2: DPI support

6

CAPI2 is now established, but one thing that's missing from CAPI1-days is the ability to compile DPI libraries. What I'm looking for is: - Specify a set of C/C++ source...

Support include paths beyond is_include_file

10

(Forwarding this from an internal bug report.) DV packages could have 100s of included files (these are not headers, but SV classes). For compilation, all that's needed is the path...

Only set a vlogdefine, do not assign a value to it

2

Goal: have fusesoc pass a define as "being set/defined" to a tool, do not assign a value to it. Currently we have code like this: ```yaml parameters: SYNTHESIS: datatype: str...

Generators can create new cores. Currently, the source files listed in these cores are inserted into the file list, but the dependencies (as listed in the `depend` statements) ignored. This...

[doc] Document use flags

1

FuseSoC supports use flags, but doesn't document which use flags are actually set. This needs to be documented. Currently we set: - A target use flag target_TARGETNAME, e.g. `target_sim` if...

FuseSoC currently does one (and after #391 two) dependency resolution runs, and expects to be able to fully resolve all dependencies in that run. With generators adding dynamicity to the...

Move FuseSoC configuration on Windows to APPDATA/LOCALAPPDATA

2

Currently, FuseSoC stores its configuration file under Windows at `~/.config`, which resolves normally to something like `C:\Users\john\.config`. Until #447 we documented we'd put the config into LOCALAPPDATA, but actually put...