m-kru
m-kru
@eine I feel like there are quite a few, general questions in your comment. As I use Vivado backend quite extensively I am sure I am able to answer some...
One more idea came to my mind, that does not break backward compatibility. An option to specify `system-name` key in the `.core` file. If given target has `system-name` key then...
Do you have an error message for `ghdl -i` when `-lgcov` is added?
@imphil done.
@imphil > It's a rather rare use case IMO, meaning we set a "default" which is rarely correct. In most cases, the target is named synth or sim, and the...
@olofk adding `-j` would make the user interface more unified. Right now user needs to remember that one tool requires `jobs` the other one `threads` and yet another one `tasks`....
The `-j` would be an option of FuseSoc, then it would create proper option for backends. In case of Makefile it would be `j` in case of Vivado `jobs` in...
@imphil > I don't see a way of making "-j" work coherently for all supported simulators. Not because the perfect scenario isn't achievable, but because I don't even see a...
@olofk I have prepared PR for edalize https://github.com/olofk/edalize/pull/222.
The best way is probably to add support for optionally defining target in the dependency. You are not the only missing this feature. Somehow no one has ever added this....