The problem is similar to #5 the current autotools makefile in Verilator is no haven.
The Verilator as a library would be very usefull for the info about the circuit. Without it lots of template based check has to be performed. (because there are not clear rules how Verilator optimizes the circuit).
The second goal is to create a Verilator based interpret so we do not have to compile a simple circuits for a simple test as compilation takes >>> more time than a test itself. And this definitely can not be done with the current Verilator. (Verilator code interpret is not so big deal (as it seems) after everything is accessible.)
The question is if we want to invest 20h+ on creating of the library target in autotool or we use existing meson which is significantly more clean.
The problem is similar to #5 the current autotools makefile in Verilator is no haven.
The Verilator as a library would be very usefull for the info about the circuit. Without it lots of template based check has to be performed. (because there are not clear rules how Verilator optimizes the circuit).
The second goal is to create a Verilator based interpret so we do not have to compile a simple circuits for a simple test as compilation takes >>> more time than a test itself. And this definitely can not be done with the current Verilator. (Verilator code interpret is not so big deal (as it seems) after everything is accessible.)
The question is if we want to invest 20h+ on creating of the library target in autotool or we use existing meson which is significantly more clean.