Olof Kindgren

@proppy That look great to me. The cue files are very readable. Happy to move forward with this. Despite the heavy use of Python within this generation of FOSSi EDA...

Yes @proppy . Let's keep it in Edalize for now. And cue files for CAPI2 core files would be fantastic. I want to kill myself every time I need to...

https://github.com/olofk/edalize/issues/293 seems to be yet another reason to get rid of makefiles

I'm all for this, and I see it as part of a general effort to add support for adding different parser frontends to Edalize. Other tools in this family include...

With the new Edalize architecture starting to fall in place I think it's a good opportunity to revisit this. I added support for using sv2v as a frontend yesterday to...

Very good point about the phony targets. I want to avoid adding Makefile-specific things because, as you noted, I want to eventually support other flow executioners (first ninja, but also...

I don't think so. This one https://github.com/olofk/edalize/wiki/Edalize-(Slight-return) only mentions ninja in passing, but not the grand vision of separating the flow from the execution of the individual tools

We should definitely fix this. I was just made aware of it last week or so when @qarlosalberto pointed out that some options weren't documented. Ok, made aware probably isn't...

Sorry. I completely missed this. It sounds like you have found a good fix. Icarus has the same behaviour actually. Theoretically this can be a problem with designs that have...

Thanks for chiming in @PeterCDMcLean . It's good to know that the code for the current support for multiple toplevels at least isn't unused :) I see three ways of...