shaba/virt-viewer
1
0
Fork 0
mirror of https://gitlab.com/virt-viewer/virt-viewer.git synced 2025-01-06 13:17:45 +03:00
Code Issues Projects Releases Wiki Activity
0f44b80d1e
virt-viewer/mingw-virt-viewer.spec.in

168 lines
5.0 KiB
RPMSpec
Raw Normal View History

mingw: Fix typo in mingw macro name (hedder -> header)
2012-12-13 21:14:30 +04:00
%{?mingw_package_header}
Convert to use Mingw64 toolchain for Windows biulds
2012-09-14 20:34:53 +04:00
Bump version 1.0 to simplify Windows MSI versioning The Windows MSI product version is restricted to a 3 component version number, whose fields are a max value of 255.255.65536 Since the main virt-viewer version takes up 3 components already, we have the munge the micro version together with the first component of the release version. eg we have $VERSION[0].$VERSION[1].($VERSION[2] << 8 + $RELEASE[0]) This causes problems for RHEL which needs to have 2-component release versions to deal with z-stream builds. eg a RHEL version might be virt-viewer-0.5.6-2.el6_4.3 and we've no easy way of adding the final '.3' to the Windows product version. If we reduce the primary virt-viewer version to just 2 components, then we can leave the 3rd component for exclusive use by the RPM release number. eg so we'd make product version up using $VERSION[0].$VERSION[1].($RELEASE[0] << 8 + $RELEASE[1]) In course of normal development, we'd increase the $VERSION[0] for each release. ie next release is 1.0, then 2.0, then 3.0. This means we retain the ability to put out "stable" branch releases for any historical version by doing 1.1, 1.2 instead of having to re-add a 3rd component. Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
2014-06-09 14:48:52 +04:00
%define relver 1%{?dist}
# We want the 1st part of the release number, and
spec: Drop %{extra_release} It was mainly meant to be used for automatic builds through Test::AutoBuild, so it can be removed now. Signed-off-by: Andrea Bolognani <abologna@redhat.com>
2018-05-07 17:40:31 +03:00
# the 3rd part (or 0 if not present).
Bump version 1.0 to simplify Windows MSI versioning The Windows MSI product version is restricted to a 3 component version number, whose fields are a max value of 255.255.65536 Since the main virt-viewer version takes up 3 components already, we have the munge the micro version together with the first component of the release version. eg we have $VERSION[0].$VERSION[1].($VERSION[2] << 8 + $RELEASE[0]) This causes problems for RHEL which needs to have 2-component release versions to deal with z-stream builds. eg a RHEL version might be virt-viewer-0.5.6-2.el6_4.3 and we've no easy way of adding the final '.3' to the Windows product version. If we reduce the primary virt-viewer version to just 2 components, then we can leave the 3rd component for exclusive use by the RPM release number. eg so we'd make product version up using $VERSION[0].$VERSION[1].($RELEASE[0] << 8 + $RELEASE[1]) In course of normal development, we'd increase the $VERSION[0] for each release. ie next release is 1.0, then 2.0, then 3.0. This means we retain the ability to put out "stable" branch releases for any historical version by doing 1.1, 1.2 instead of having to re-add a 3rd component. Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
2014-06-09 14:48:52 +04:00
# This scheme lets us cope with RHEL-style z-stream
# versioning when creating Win product versions
%define rel0 %(echo %{relver} | cut -d. -f1)
%define rel1 %(test -z "`echo %{relver} | cut -d. -f3`" && echo 0 || (echo %{relver} | cut -d. -f3))
%define buildid %(expr %{rel0} \\* 256 + %{rel1})
rpm: include buildid components in MSI filename The MSI file can contain different content with each change in build ID, but the filename never changes. This creates confusion as to whether the MSI is actually up to date or not. It requires the looking inside the MSI to see the encoded version. The RPM uses 2 components from the %release field as input for the build ID value. Use these as two parts of the filename, separated from the version with a "-" similar to how RPM version/release are separated. IOW, an RPM mingw32-virt-viewer-msi-9.0-1.fc33.noarch.rpm will result in virt-viewer-x64-9.0-1.0.msi while mingw32-virt-viewer-msi-9.0-1.fc33.1.noarch.rpm will result in virt-viewer-x64-9.0-1.1.msi Essentially we've just stripped the %dist part (".fc33") out of the release, and default the second component to "0" if omitted. Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
2021-02-22 21:07:52 +03:00
%define msiver @VERSION@-%{rel0}.%{rel1}
Convert to use Mingw64 toolchain for Windows biulds
2012-09-14 20:34:53 +04:00
Name: mingw-virt-viewer
Version: @VERSION@
spec: Drop %{extra_release} It was mainly meant to be used for automatic builds through Test::AutoBuild, so it can be removed now. Signed-off-by: Andrea Bolognani <abologna@redhat.com>
2018-05-07 17:40:31 +03:00
Release: %{relver}
Convert to use Mingw64 toolchain for Windows biulds
2012-09-14 20:34:53 +04:00
Summary: MinGW Windows virt-viewer console application
rpm: convert license to SPDX format Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
2023-04-26 19:47:19 +03:00
License: GPL-2.0-or-later
rpm: use https for URLs Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
2021-01-11 18:36:50 +03:00
URL: https://gitlab.com/virt-viewer/virt-viewer
rpm: convert the RPM builds over to using meson Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
2021-01-11 18:58:25 +03:00
Source0: https://virt-manager.org/download/sources/virt-viewer/virt-viewer-%{version}.tar.xz
Convert to use Mingw64 toolchain for Windows biulds
2012-09-14 20:34:53 +04:00
rpm: convert the RPM builds over to using meson Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
2021-01-11 18:58:25 +03:00
BuildRequires: meson
msi: Depend on mingw-adwaita-icon-theme Instead of maintain a file which includes every single icon that we use from adwaita-icon-theme (adwaita-icons-needed.wxi.in), let's depend on mingw-adwaita-icon-theme directly. It reduces considerably the maintainability and the risk to have missing icons. Although, the size of the final binary gets increased from ~35MB to ~50MB. Resolves: rhbz#1301064 Signed-off-by: Fabiano Fidêncio <fidencio@redhat.com> Acked-by: Christophe Fergeau <cfergeau@redhat.com>
2016-04-26 15:36:57 +03:00
BuildRequires: mingw32-adwaita-icon-theme
BuildRequires: mingw64-adwaita-icon-theme
rpm: remove version numbers from deps We can assume that the distros we target have sufficiently new versions of all our dependencies. Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
2021-01-11 18:35:22 +03:00
BuildRequires: mingw32-filesystem
BuildRequires: mingw64-filesystem
BuildRequires: mingw32-glib2
BuildRequires: mingw64-glib2
Add deps on mingw glib-networking RPMs needed by libsoup
2015-01-09 14:13:30 +03:00
BuildRequires: mingw32-glib-networking
BuildRequires: mingw64-glib-networking
mingw,spec: Fix mingw-gstreamer1-plugins-bad-free name The package was created with a wrong name (mingw-gstreamer1-plugins-bad) and then fixed (mingw-gstreamer1-plugins-bad-free) for f22 and newer.
2015-06-24 15:34:48 +03:00
BuildRequires: mingw32-gstreamer1-plugins-bad-free
BuildRequires: mingw64-gstreamer1-plugins-bad-free
Update mingw RPM deps to refer to gstreamer1
2015-01-09 13:51:45 +03:00
BuildRequires: mingw32-gstreamer1-plugins-good
BuildRequires: mingw64-gstreamer1-plugins-good
rpm: remove version numbers from deps We can assume that the distros we target have sufficiently new versions of all our dependencies. Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
2021-01-11 18:35:22 +03:00
BuildRequires: mingw32-gtk3
BuildRequires: mingw64-gtk3
rpm: use the mingw hicolor icon theme not native Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
2019-03-01 18:33:20 +03:00
BuildRequires: mingw32-hicolor-icon-theme
BuildRequires: mingw64-hicolor-icon-theme
spec: Update mingw in order to use ovirt
2014-12-23 02:57:44 +03:00
BuildRequires: mingw32-libgovirt
BuildRequires: mingw64-libgovirt
mingw: Add packages for virt-viewer NSIS installer This makes it much easier to build an updated Windows installer binary as this can now be done using mock/koji/... by using this .spec and a virt-viewer tarball.
2012-12-13 21:14:54 +04:00
BuildRequires: mingw32-libusbx
BuildRequires: mingw64-libusbx
rpm: remove version numbers from deps We can assume that the distros we target have sufficiently new versions of all our dependencies. Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
2021-01-11 18:35:22 +03:00
BuildRequires: mingw32-libvirt
BuildRequires: mingw64-libvirt
BuildRequires: mingw32-libvirt-glib
BuildRequires: mingw64-libvirt-glib
BuildRequires: mingw32-libxml2
BuildRequires: mingw64-libxml2
BuildRequires: mingw32-gtk-vnc2
BuildRequires: mingw64-gtk-vnc2
mingw: Add packages for virt-viewer NSIS installer This makes it much easier to build an updated Windows installer binary as this can now be done using mock/koji/... by using this .spec and a virt-viewer tarball.
2012-12-13 21:14:54 +04:00
BuildRequires: mingw32-readline
BuildRequires: mingw64-readline
spec: Update mingw in order to use ovirt
2014-12-23 02:57:44 +03:00
BuildRequires: mingw32-rest
BuildRequires: mingw64-rest
mingw: Add packages for virt-viewer NSIS installer This makes it much easier to build an updated Windows installer binary as this can now be done using mock/koji/... by using this .spec and a virt-viewer tarball.
2012-12-13 21:14:54 +04:00
BuildRequires: mingw32-spice-glib
BuildRequires: mingw64-spice-glib
rpm: remove version numbers from deps We can assume that the distros we target have sufficiently new versions of all our dependencies. Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
2021-01-11 18:35:22 +03:00
BuildRequires: mingw32-spice-gtk3
BuildRequires: mingw64-spice-gtk3
mingw: Add packages for virt-viewer NSIS installer This makes it much easier to build an updated Windows installer binary as this can now be done using mock/koji/... by using this .spec and a virt-viewer tarball.
2012-12-13 21:14:54 +04:00
BuildRequires: mingw32-usbredir
BuildRequires: mingw64-usbredir
Convert to use Mingw64 toolchain for Windows biulds
2012-09-14 20:34:53 +04:00
BuildRequires: pkgconfig
build-sys: generate MSI installer instead of NSIS
2013-04-03 16:02:30 +04:00
BuildRequires: /usr/bin/pod2man
po: provide custom make rules for po file management Historically we have relied on intltool to install a standard po/Makefile.in.in which has very limited scope for customization. intltool is deprecated in favour of standard gettextize tools, but these share the same disadvantages. Writing make rules for po file management is no more difficult than any other rules virt-viewer has, so stop using intltool and don't use gettextize ether. Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
2019-02-20 18:19:43 +03:00
BuildRequires: gettext
mingw: Add packages for virt-viewer NSIS installer This makes it much easier to build an updated Windows installer binary as this can now be done using mock/koji/... by using this .spec and a virt-viewer tarball.
2012-12-13 21:14:54 +04:00
BuildRequires: icoutils
BuildRequires: dos2unix
spec: Update mingw in order to use gtk3
2014-12-23 02:55:58 +03:00
BuildRequires: hwdata
rpm: remove version numbers from deps We can assume that the distros we target have sufficiently new versions of all our dependencies. Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
2021-01-11 18:35:22 +03:00
BuildRequires: msitools
Add glib2-devel for mingw build The native glib2-devel package is needed for mingw builds in order to get the glib-compile-schemas binary. Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
2019-03-01 18:27:28 +03:00
BuildRequires: glib2-devel
Convert to use Mingw64 toolchain for Windows biulds
2012-09-14 20:34:53 +04:00
BuildArch: noarch
%package -n mingw32-virt-viewer
Summary: MinGW Windows virt-viewer console application
Group: Applications/Internet
%package -n mingw64-virt-viewer
Summary: MinGW Windows virt-viewer console application
Group: Applications/Internet
build-sys: generate MSI installer instead of NSIS
2013-04-03 16:02:30 +04:00
%package -n mingw64-virt-viewer-msi
Summary: MinGW Windows virt-viewer MSI
mingw: Add packages for virt-viewer NSIS installer This makes it much easier to build an updated Windows installer binary as this can now be done using mock/koji/... by using this .spec and a virt-viewer tarball.
2012-12-13 21:14:54 +04:00
Group: Applications/Internet
build-sys: generate MSI installer instead of NSIS
2013-04-03 16:02:30 +04:00
%package -n mingw32-virt-viewer-msi
Summary: MinGW Windows virt-viewer MSI
mingw: Add packages for virt-viewer NSIS installer This makes it much easier to build an updated Windows installer binary as this can now be done using mock/koji/... by using this .spec and a virt-viewer tarball.
2012-12-13 21:14:54 +04:00
Group: Applications/Internet
Convert to use Mingw64 toolchain for Windows biulds
2012-09-14 20:34:53 +04:00
%description
MinGW Windows virt-viewer console application
%description -n mingw32-virt-viewer
MinGW Windows virt-viewer console application
%description -n mingw64-virt-viewer
MinGW Windows virt-viewer console application
build-sys: generate MSI installer instead of NSIS
2013-04-03 16:02:30 +04:00
%description -n mingw64-virt-viewer-msi
MinGW Windows virt-viewer MSI
mingw: Add packages for virt-viewer NSIS installer This makes it much easier to build an updated Windows installer binary as this can now be done using mock/koji/... by using this .spec and a virt-viewer tarball.
2012-12-13 21:14:54 +04:00
build-sys: generate MSI installer instead of NSIS
2013-04-03 16:02:30 +04:00
%description -n mingw32-virt-viewer-msi
MinGW Windows virt-viewer MSI
mingw: Add packages for virt-viewer NSIS installer This makes it much easier to build an updated Windows installer binary as this can now be done using mock/koji/... by using this .spec and a virt-viewer tarball.
2012-12-13 21:14:54 +04:00
mingw: Package debug files When building on f18, the build fails because of unpackaged debug files. Use the appropriate mingw macro to generate the mingw debug packages. The build failure is: RPM build errors: error: Installed (but unpackaged) file(s) found: /usr/i686-w64-mingw32/sys-root/mingw/bin/debug-helper.exe.debug /usr/i686-w64-mingw32/sys-root/mingw/bin/remote-viewer.exe.debug /usr/i686-w64-mingw32/sys-root/mingw/bin/virt-viewer.exe.debug /usr/i686-w64-mingw32/sys-root/mingw/bin/windows-cmdline-wrapper.exe.debug /usr/x86_64-w64-mingw32/sys-root/mingw/bin/debug-helper.exe.debug /usr/x86_64-w64-mingw32/sys-root/mingw/bin/remote-viewer.exe.debug /usr/x86_64-w64-mingw32/sys-root/mingw/bin/virt-viewer.exe.debug /usr/x86_64-w64-mingw32/sys-root/mingw/bin/windows-cmdline-wrapper.exe.debug Installed (but unpackaged) file(s) found: /usr/i686-w64-mingw32/sys-root/mingw/bin/debug-helper.exe.debug /usr/i686-w64-mingw32/sys-root/mingw/bin/remote-viewer.exe.debug /usr/i686-w64-mingw32/sys-root/mingw/bin/virt-viewer.exe.debug /usr/i686-w64-mingw32/sys-root/mingw/bin/windows-cmdline-wrapper.exe.debug /usr/x86_64-w64-mingw32/sys-root/mingw/bin/debug-helper.exe.debug /usr/x86_64-w64-mingw32/sys-root/mingw/bin/remote-viewer.exe.debug /usr/x86_64-w64-mingw32/sys-root/mingw/bin/virt-viewer.exe.debug /usr/x86_64-w64-mingw32/sys-root/mingw/bin/windows-cmdline-wrapper.exe.debug
2012-12-21 18:24:42 +04:00
%{mingw_debug_package}
Convert to use Mingw64 toolchain for Windows biulds
2012-09-14 20:34:53 +04:00
%prep
%setup -q -n virt-viewer-%{version}
%build
rpm: fix passing of build-id parameter Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
2021-02-12 21:14:17 +03:00
%mingw_meson -Dbuild-id=%{buildid}
rpm: convert the RPM builds over to using meson Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
2021-01-11 18:58:25 +03:00
%mingw_ninja
build-sys: generate MSI installer instead of NSIS
2013-04-03 16:02:30 +04:00
rpm: convert the RPM builds over to using meson Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
2021-01-11 18:58:25 +03:00
%if 0%{?mingw_build_win32} == 1
%endif
%if 0%{?mingw_build_win64} == 1
%endif
Convert to use Mingw64 toolchain for Windows biulds
2012-09-14 20:34:53 +04:00
%install
rpm: convert the RPM builds over to using meson Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
2021-01-11 18:58:25 +03:00
%mingw_ninja_install
Convert to use Mingw64 toolchain for Windows biulds
2012-09-14 20:34:53 +04:00
mingw: Add packages for virt-viewer NSIS installer This makes it much easier to build an updated Windows installer binary as this can now be done using mock/koji/... by using this .spec and a virt-viewer tarball.
2012-12-13 21:14:54 +04:00
%if 0%{?mingw_build_win32} == 1
rpm: convert the RPM builds over to using meson Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
2021-01-11 18:58:25 +03:00
DESTDIR=%{buildroot} ninja -C build_win32$MINGW_BUILDDIR_SUFFIX data/virt-viewer-x86-@VERSION@.msi
Use GResource for loading ui files Let's take advantage of GResource for loading ui files in a better and cleaner way than virt_viewer_util_load_ui() was doing. It also brings the benefit, at least for developers, of being able to test ui changes without having to "make install" virt-viewer. Signed-off-by: Fabiano Fidêncio <fidencio@redhat.com> Acked-by: Eduardo Lima (Etrunko) <etrunko@redhat.com>
2016-02-26 20:08:40 +03:00
mkdir $RPM_BUILD_ROOT/%{mingw32_datadir}/virt-viewer
rpm: include buildid components in MSI filename The MSI file can contain different content with each change in build ID, but the filename never changes. This creates confusion as to whether the MSI is actually up to date or not. It requires the looking inside the MSI to see the encoded version. The RPM uses 2 components from the %release field as input for the build ID value. Use these as two parts of the filename, separated from the version with a "-" similar to how RPM version/release are separated. IOW, an RPM mingw32-virt-viewer-msi-9.0-1.fc33.noarch.rpm will result in virt-viewer-x64-9.0-1.0.msi while mingw32-virt-viewer-msi-9.0-1.fc33.1.noarch.rpm will result in virt-viewer-x64-9.0-1.1.msi Essentially we've just stripped the %dist part (".fc33") out of the release, and default the second component to "0" if omitted. Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
2021-02-22 21:07:52 +03:00
cp build_win32$MINGW_BUILDDIR_SUFFIX/data/virt-viewer-x86-@VERSION@.msi $RPM_BUILD_ROOT/%{mingw32_datadir}/virt-viewer/virt-viewer-x86-%{msiver}.msi
mingw: Add packages for virt-viewer NSIS installer This makes it much easier to build an updated Windows installer binary as this can now be done using mock/koji/... by using this .spec and a virt-viewer tarball.
2012-12-13 21:14:54 +04:00
%endif
%if 0%{?mingw_build_win64} == 1
rpm: convert the RPM builds over to using meson Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
2021-01-11 18:58:25 +03:00
DESTDIR=%{buildroot} ninja -C build_win64$MINGW_BUILDDIR_SUFFIX data/virt-viewer-x64-@VERSION@.msi
Use GResource for loading ui files Let's take advantage of GResource for loading ui files in a better and cleaner way than virt_viewer_util_load_ui() was doing. It also brings the benefit, at least for developers, of being able to test ui changes without having to "make install" virt-viewer. Signed-off-by: Fabiano Fidêncio <fidencio@redhat.com> Acked-by: Eduardo Lima (Etrunko) <etrunko@redhat.com>
2016-02-26 20:08:40 +03:00
mkdir $RPM_BUILD_ROOT/%{mingw64_datadir}/virt-viewer
rpm: include buildid components in MSI filename The MSI file can contain different content with each change in build ID, but the filename never changes. This creates confusion as to whether the MSI is actually up to date or not. It requires the looking inside the MSI to see the encoded version. The RPM uses 2 components from the %release field as input for the build ID value. Use these as two parts of the filename, separated from the version with a "-" similar to how RPM version/release are separated. IOW, an RPM mingw32-virt-viewer-msi-9.0-1.fc33.noarch.rpm will result in virt-viewer-x64-9.0-1.0.msi while mingw32-virt-viewer-msi-9.0-1.fc33.1.noarch.rpm will result in virt-viewer-x64-9.0-1.1.msi Essentially we've just stripped the %dist part (".fc33") out of the release, and default the second component to "0" if omitted. Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
2021-02-22 21:07:52 +03:00
cp build_win64$MINGW_BUILDDIR_SUFFIX/data/virt-viewer-x64-@VERSION@.msi $RPM_BUILD_ROOT/%{mingw64_datadir}/virt-viewer/virt-viewer-x64-%{msiver}.msi
mingw: Add packages for virt-viewer NSIS installer This makes it much easier to build an updated Windows installer binary as this can now be done using mock/koji/... by using this .spec and a virt-viewer tarball.
2012-12-13 21:14:54 +04:00
%endif
Convert to use Mingw64 toolchain for Windows biulds
2012-09-14 20:34:53 +04:00
%find_lang virt-viewer
%files -n mingw32-virt-viewer -f virt-viewer.lang
%defattr(-,root,root)
%{mingw32_bindir}/virt-viewer.exe
%{mingw32_bindir}/remote-viewer.exe
%{mingw32_bindir}/windows-cmdline-wrapper.exe
%dir %{mingw32_datadir}/virt-viewer/
%{mingw32_datadir}/icons/hicolor/*/apps/*
%{mingw32_mandir}/man1/virt-viewer.1*
%{mingw32_mandir}/man1/remote-viewer.1*
build-sys: generate MSI installer instead of NSIS
2013-04-03 16:02:30 +04:00
%files -n mingw32-virt-viewer-msi
rpm: include buildid components in MSI filename The MSI file can contain different content with each change in build ID, but the filename never changes. This creates confusion as to whether the MSI is actually up to date or not. It requires the looking inside the MSI to see the encoded version. The RPM uses 2 components from the %release field as input for the build ID value. Use these as two parts of the filename, separated from the version with a "-" similar to how RPM version/release are separated. IOW, an RPM mingw32-virt-viewer-msi-9.0-1.fc33.noarch.rpm will result in virt-viewer-x64-9.0-1.0.msi while mingw32-virt-viewer-msi-9.0-1.fc33.1.noarch.rpm will result in virt-viewer-x64-9.0-1.1.msi Essentially we've just stripped the %dist part (".fc33") out of the release, and default the second component to "0" if omitted. Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
2021-02-22 21:07:52 +03:00
%{mingw32_datadir}/virt-viewer/virt-viewer-x86-%{msiver}.msi
mingw: Add packages for virt-viewer NSIS installer This makes it much easier to build an updated Windows installer binary as this can now be done using mock/koji/... by using this .spec and a virt-viewer tarball.
2012-12-13 21:14:54 +04:00
Convert to use Mingw64 toolchain for Windows biulds
2012-09-14 20:34:53 +04:00
%files -n mingw64-virt-viewer -f virt-viewer.lang
%defattr(-,root,root)
%{mingw64_bindir}/virt-viewer.exe
%{mingw64_bindir}/remote-viewer.exe
%{mingw64_bindir}/windows-cmdline-wrapper.exe
%dir %{mingw64_datadir}/virt-viewer/
%{mingw64_datadir}/icons/hicolor/*/apps/*
%{mingw64_mandir}/man1/virt-viewer.1*
%{mingw64_mandir}/man1/remote-viewer.1*
build-sys: generate MSI installer instead of NSIS
2013-04-03 16:02:30 +04:00
%files -n mingw64-virt-viewer-msi
rpm: include buildid components in MSI filename The MSI file can contain different content with each change in build ID, but the filename never changes. This creates confusion as to whether the MSI is actually up to date or not. It requires the looking inside the MSI to see the encoded version. The RPM uses 2 components from the %release field as input for the build ID value. Use these as two parts of the filename, separated from the version with a "-" similar to how RPM version/release are separated. IOW, an RPM mingw32-virt-viewer-msi-9.0-1.fc33.noarch.rpm will result in virt-viewer-x64-9.0-1.0.msi while mingw32-virt-viewer-msi-9.0-1.fc33.1.noarch.rpm will result in virt-viewer-x64-9.0-1.1.msi Essentially we've just stripped the %dist part (".fc33") out of the release, and default the second component to "0" if omitted. Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
2021-02-22 21:07:52 +03:00
%{mingw64_datadir}/virt-viewer/virt-viewer-x64-%{msiver}.msi
mingw: Add packages for virt-viewer NSIS installer This makes it much easier to build an updated Windows installer binary as this can now be done using mock/koji/... by using this .spec and a virt-viewer tarball.
2012-12-13 21:14:54 +04:00
Convert to use Mingw64 toolchain for Windows biulds
2012-09-14 20:34:53 +04:00
%changelog
Reference in New Issue Copy Permalink