Stephen Williams wrote:
Günter Dannoritzer wrote:
[...]
This is for users who have a 32bit .vpi module from a 3'rd party. They
cannot use it with the 64bit vvp, but vvp32 will be able to load it
just fine. That's the *only* reason for vvp32.
OK, I understand, so for a rpm package that
Günter Dannoritzer wrote:
Stephen Williams wrote:
To add an add-on like a vpi package, you don't need to rebuild
the Icarus Verilog package! Just have the myhdl rpm drop the .vpi
in the right directory at install time. How does that affect Icarus
Verilog packaging?
Yes, I undestand that.
Stephen Williams wrote:
The way you handle that is to create a sub-package that depends on
Icarus Verilog. Users can install your main package without requiring
Icarus Verilog, but if they install the icarus verilog interface, they
will naturally require the Icarus Verilog package.
You
Günter Dannoritzer wrote:
One change done by Werner Hoch is to add build requires depending on
x86_64. I added another BuildRequires for openSuse 10.2:
-
%ifarch x86_64
BuildRequires: bzip2-32bit, glibc-devel-32bit, glibc-32bit, zlib-devel-32bit
BuildRequires: termcap-32bit,
4 matches
Mail list logo
