Force forward slash paths - Verilator on Cygwin about edalize HOT 6 CLOSED

Let's get that fixed. Over time I have come to realize that most of the EDA tools actually only use forward slashes even on Windows. I'd say it's a blessing in the greater scheme of things but it causes some edge cases. Would highly appreciate if someone could step up and tell me how to do a proper cygwin detection and what the situation is on e.g. WSL

from edalize.

WSL works fine - its far more isolated from the rest of the windows system, eg when you access files on the Windows part its via a mount of your whole drive in Linux as opposed to Cygwin which (I think) just accesses it directly through the windows system calls dressed up like Linux ones.

Would wlecome any input from someone more familar with the OS internals than I however :)

from edalize.

This got me wondering if there are any cases at all where verilator needs back slash. Perhaps we can just force forward slashes and not to any platform detection at all. Any clues @wsnyder ?

from edalize.

Verilator always assumes forward slashes separate paths. A backslash in a file list (.vc) file is typically used to quote a quote, e.g. """), which Verilator understands, as do several but not all commercial simulators.

from edalize.

Thanks @wsnyder! @AlistairSymonds, I just pushed a patch for edalize now. Please let me know if that helps

from edalize.

I believe this one can be closed. Reopen if problem remains

from edalize.