al davis wrote: > The issue now, with plugins and VHDL/Verilog behavioral > modeling, is that a lot more is required. In the future, you > will need to have a C++ compiler installed to be able to fully > run gnucap, unless you stick to a subset of what it can do. > Even with a subset, it will still rely on run time dynamic > linking on demand.
Icarus Verilog has (and solves) all those problems. VPI modules are dynamically loaded (works under Windows) and the package provides iverilog-vpi to compile VPI/PLI modules for the user. Really, it's not shockingly difficult if you stay away from the M$ tools. > This is the windows problem, Making sure the whole environment > including compilers and dynamic linking all works together. I > think cygwin will be a requirement. The Icarus Verilog Windows installer checks for the mingw32 compiler and marks the registry so that the iverilog-vpi program can find it. Otherwise, it's no big deal. In fact, I am of the opinion that it is best to *not* use Cygwin for anything you are going to distribute, except as a last resort. The user should be allowed to use Cygwin, but not expected to have it. Really, dynamic linking is easy in every O/S out there, these days. (With the possible exception of HP/UX. Ugh!) -- Steve Williams "The woods are lovely, dark and deep. steve at icarus.com But I have promises to keep, http://www.icarus.com and lines to code before I sleep, http://www.picturel.com And lines to code before I sleep." _______________________________________________ geda-dev mailing list [email protected] http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev
