public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Filipe Rosset <rosset.filipe@gmail.com>
To: git-commits@fedoraproject.org
Subject: [rpms/iverilog] f44: split iverilog in devel, static and binary packages
Date: Tue, 09 Jun 2026 00:10:22 GMT [thread overview]
Message-ID: <178096382253.1.11937653374204254627.rpms-iverilog-1d1f9752e10c@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/iverilog
Branch : f44
Commit : 1d1f9752e10c8d4c8f39c238f0f016adc7c63a13
Author : Filipe Rosset <rosset.filipe@gmail.com>
Date : 2026-06-08T20:49:47-03:00
Stats : +37/-30 in 1 file(s)
URL : https://src.fedoraproject.org/rpms/iverilog/c/1d1f9752e10c8d4c8f39c238f0f016adc7c63a13?branch=f44
Log:
split iverilog in devel, static and binary packages
---
diff --git a/iverilog.spec b/iverilog.spec
index 8358d6b..3db2ac2 100644
--- a/iverilog.spec
+++ b/iverilog.spec
@@ -1,6 +1,6 @@
Name: iverilog
Version: 13.0
-%define uver 13_0
+%global uver 13_0
Release: %autorelease
Summary: Icarus Verilog is a verilog compiler and simulator
@@ -27,11 +27,30 @@ engineering formats, including simulation. It strives to be true
to the IEEE-1364 standard.
+%package devel
+Summary: Header files for Icarus Verilog development
+Requires: %{name}%{?_isa} = %{version}-%{release}
+
+%description devel
+This package contains the header files needed to develop VPI/PLI modules
+for Icarus Verilog.
+
+
+%package static
+Summary: Static libraries for Icarus Verilog development
+Requires: %{name}-devel%{?_isa} = %{version}-%{release}
+
+%description static
+This package contains the static libraries needed to develop VPI/PLI modules
+for Icarus Verilog.
+
+
%prep
%autosetup -n %{name}-%{uver}
-# Clean junks from tarball
-find . -type f -name ".git" -exec rm '{}' \;
-rm -rf `find . -type d -name "autom4te.cache" -exec echo '{}' \;`
+# Clean junk files from tarball
+find . -name .git -exec rm -rf {} +
+find . -name autom4te.cache -exec rm -rf {} +
+
%build
%configure
@@ -39,46 +58,34 @@ rm -rf `find . -type d -name "autom4te.cache" -exec echo '{}' \;`
# Build Sphinx documentation as well
%make_build -C Documentation html
+rm -f Documentation/_build/html/.buildinfo
+
-
%install
-%{__make} prefix=%{buildroot}%{_prefix} \
- bindir=%{buildroot}%{_bindir} \
- libdir=%{buildroot}%{_libdir} \
- libdir64=%{buildroot}%{_libdir} \
- includedir=%{buildroot}%{_includedir} \
- mandir=%{buildroot}%{_mandir} \
- pdfdir=%{buildroot}%{_pdfdir}/ivl/ \
- vpidir=%{buildroot}%{_libdir}/ivl/ \
- INSTALL="install -p" \
-install
-
-
-# Install HTML documentation
-rm -rf Documentation/_build/html/.buildinfo
-mkdir -p %{buildroot}%{_docdir}/%{name}
-cp -r Documentation/_build/html %{buildroot}%{_docdir}/%{name}
-
-
+%make_install INSTALL="install -p"
+
+
%check
make check
-
-
+
+
%files
%license COPYING
-%doc examples html README.md
+%doc README.md examples Documentation/_build/html
%{_bindir}/iverilog
%{_bindir}/iverilog-vpi
%{_bindir}/vvp
%{_libdir}/ivl
%{_mandir}/man1/*
-# headers for PLI: This is intended to be used by the user.
-%{_includedir}/*.h
-# RHBZ 480531
+%files devel
+%{_includedir}/iverilog/
+
+
+%files static
%{_libdir}/*.a
-
+
%changelog
%autochangelog
reply other threads:[~2026-06-09 0:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=178096382253.1.11937653374204254627.rpms-iverilog-1d1f9752e10c@fedoraproject.org \
--to=rosset.filipe@gmail.com \
--cc=git-commits@fedoraproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox