Closed xobs closed 4 years ago
Also, I see there was a question about why I removed verilated_command_args_add()
, but I can't see it now. I removed it because it wasn't present in my version of verilator. It looks like things got moved around in https://github.com/verilator/verilator/commit/84335b958015c2b15266cfbcc1b0a87b2d035c30 and as a result it doesn't actually get linked in.
Specifically, with that function call still in place, I get the following error:
[11:09:06 AM] D:/Code/verilated-rs> cargo run
Compiling verilated v0.1.1 (D:\Code\verilated-rs\verilated)
Compiling example v0.0.0 (D:\Code\verilated-rs\example)
error: linking with `link.exe` failed: exit code: 1120
|
= note: "C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\ [...] "msvcrt.lib"
= note: libverilated-5150819e2e36f022.rlib(verilated_shim.o) : error LNK2019: unresolved external symbol "public: stat
ic void __cdecl Verilated::commandArgsAdd(int,char const * *)" (?commandArgsAdd@Verilated@@SAXHPEAPEBD@Z) referenced in
function verilated_command_args_add
D:\Code\verilated-rs\target\debug\deps\example.exe : fatal error LNK1120: 1 unresolved externals
error: aborting due to previous error
error: could not compile `example`.
To learn more, run the command again with --verbose.
[11:09:19 AM] D:/Code/verilated-rs>
This adds some patches to get
verilated-rs
running on Windows: