Olof Kindgren

I guess the main problem is that checking in fusesoc.conf is not an intended use-case. It does seem like it _almost_ works though, so let's try to make what you're...

Library managment in FuseSoC could need some more love in general. The use-case you describe just wasn't considered by anyone. The assumption was that the workspace directory is a throw-away...

Sorry about that. I remember having some headaches trying to get the ghdl backend working. Since I'm not a regular ghdl user myself, it's harder to see if I have...

Generally, we try to avoid adding explicit options when there are other ways to accomplish the same thing. The reason for that is there would otherwise be a million different...

I understand your point, but one reflection I have made over the 12 years I have been working on this is that people are using these tools in such incredibly...

There seems to be issues still I tried it with an old VHDL example that I put together for other reasons a couple of years ago. Attaching the example project...

Sorry. I never got back to this one. Are we all good at this point, or are there any issues remaining? Did I understand correctly that this requires `work` to...

Wrote a response in https://github.com/TerosTechnology/vscode-terosHDL/issues/472 but forgot to write here. Do we need `-p` at all?

Thanks for this. Highly appreciate the well-structured commits! It looks great overall, but I have some questions/comments on the programmer addition. Do we need to specify all these parameters for...

It is supposed to work with all tools, but you're right, it's currently broken in the ghdl backend