I added today pull up support in simulavr for verilog. This feature can
only be used with Icarus Verilog version v10 or higher.
As a result we can expect that users will install the new version in
parallel with the old verilog version.
That will result in conflicts to find executable's and header files (
vpi_user.h ). Building simulavr works with manual setting the include
path like
CPPFLAGS=-I/opt/verilog/v10/include/ ./configure --enable-tcl
--enable-verilog
but this will result in wrong example/verilog execution.
The ./configure find the standard installation executables but avr.vpi
is compiled against the new header.
It would be nice if someone can support a additional configure parameter
to add the path to an additional verilog installation for header and
executable.
Thanks!
Klaus
_______________________________________________
Simulavr-devel mailing list
Simulavr-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/simulavr-devel
