Forums » Installation »
dependency on SystemC is problematic for distributions
Added by Iztok Jeras over 2 years ago
Hi,
I must admit I have not compiled any code yet with Verilator, I first started packaging it for Ubuntu/Debian. The problem is related to SystemC, which is not packaged for the main distributions, mostly due to some licensing concerns, you have probably heard about. I would like to rant about it, but it is probably not a good idea. Fedora ElectronicLab team seems to be working on it.
So I would like to package Verilator without dependencies on SystemC. The problem is the test code, which automatically tests SystemC and System-Perl. A global configure option to disable SystemC related code sounds great to me (but I am far from being an expert). I currently have disabled tests other than test_c in my packages, so a change is not really required.
I plan to use Verilator for some of mine OpenSource projects, the feature set sounds great, but as I mentioned I did not test it jet (I will soon). I suppose I am not interested in SystemC features (but I can not be sure, since I have no experience with it). Could you define more clearly which Verilator features depend on SystemC (and System-Perl, VerilogPerl)?
I will try to do some more .deb packaging and simulation experiments, than I will contact the Debian electronics team and ask them to include the packages into Debian unstable, and help me package VerilogPerl. Packages should probably also reach the next release of Ubuntu.
Otherwise I am working at an ASIC company, trying to organize a Verilog seminar for students in Ljubljana/Slovenija and I help the Icarus Verilog team with packaging for Ubuntu/Debian.
Regards, Iztok Jeras https://launchpad.net/~iztok.jeras
Replies (1)
RE: dependency on SystemC is problematic for distributions - Added by Wilson Snyder over 2 years ago
It isn't really dependent on SystemC. You choose what your test bench is written on, C++ or SystemC (or SystemPerl) then verilate into that form. The only thing that isn't currently supported with C++ only is coverage analysis.
So, I think not packing up it with SystemC is a fine approach, if there's licensing issues. Note with 3.800 if you don't need SystemC you won't need SystemPerl nor Verilog-Perl. It looks like you've already done so, but the fedora spec files are a good starting point.
I'll change the tests to pass if there's no SystemC installed.
(1-1/1)
![[logo]](/img/veripool_small.png)