Olof Kindgren

Thank you for the report and suggested solution. Someone else noticed this issue in the [chat](https://gitter.im/librecores/fusesoc) recently. I thought the problem was that we did a clone and then a...

Ping @imphil

You're right. Documentation is very much needed. Will start writing.

I have also encountered some unforseen issues that will require an API rewrite. Specifically, changing the flow graph using flow options (e.g. adding a frontend) doesn't work very well because...

Oh, cool! I think we need to keep the tools section generic actually because that information comes from Edalize and depends on which version of Edalize is being used. Of...

Most of this is new to me so I'm still trying to wrap my head around the various options, but here are some assorted thoughts going through my head. 1....

I really want html generation like what we have here https://fusesoc.readthedocs.io/en/stable/ref/capi2.html, so that's definitely an argument for generating jsonschema files at least for now (or use those as the input...

I don't have any strong opinions but jsonschema does seem to have the most mature ecosystem and I don't think we need anything more fancy than that. I have heard...

It looks like you hit a bug. I haven't analyzed what goes on, but there is something wrong with FuseSoC here. As a workaround for now, perhaps you could set...

The most straight-forward way would be to add a new backend option to split up the `-i` and `-m` options. But! I was halfway through a rewrite of the ghdl...