So far XSim has been tested and works with a shared library. We need to determine what we need to be able to build libraries for the different simulators. Some things that are definitely come up are:
32-bit vs 64-bit (at least some versions of ModelSim are still 32-bit)
C++ ABI (again, at least some versions of ModelSim use a fantastically old compiler)
Also, I'd like to determine if it's possible to give commercial simulators static libraries instead of shared libraries. If most/all require the latter, we may want to just give up on static libraries even though it's easier for Verilator. In that case, we could add a --dpi-library-path option like the commercial simulators have so users don't have to mess around with LD_LIBRARY_PATH.
The text was updated successfully, but these errors were encountered:
Author Name: Todd Strader (@toddstrader)
Original Redmine Issue: 1517 from https://www.veripool.org
Original Assignee: Todd Strader (@toddstrader)
So far XSim has been tested and works with a shared library. We need to determine what we need to be able to build libraries for the different simulators. Some things that are definitely come up are:
Also, I'd like to determine if it's possible to give commercial simulators static libraries instead of shared libraries. If most/all require the latter, we may want to just give up on static libraries even though it's easier for Verilator. In that case, we could add a --dpi-library-path option like the commercial simulators have so users don't have to mess around with LD_LIBRARY_PATH.
The text was updated successfully, but these errors were encountered: