public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Kevin Kofler <Kevin@tigcc.ticalc.org>
To: git-commits@fedoraproject.org
Subject: [rpms/kig] epel10: work around BoostPython.cmake failure by setting variables explicitly
Date: Tue, 04 Aug 2026 19:44:47 GMT [thread overview]
Message-ID: <178587268791.1.14834511972007957250.rpms-kig-b5b40b0190ba@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/kig
Branch : epel10
Commit : b5b40b0190ba91e5599fb60f2519812f36b900b5
Author : Kevin Kofler <Kevin@tigcc.ticalc.org>
Date : 2019-10-29T14:37:03+01:00
Stats : +4/-1 in 1 file(s)
URL : https://src.fedoraproject.org/rpms/kig/c/b5b40b0190ba91e5599fb60f2519812f36b900b5?branch=epel10
Log:
work around BoostPython.cmake failure by setting variables explicitly
---
diff --git a/kig.spec b/kig.spec
index ffffcfc..6679624 100644
--- a/kig.spec
+++ b/kig.spec
@@ -72,7 +72,9 @@ pushd %{_target_platform}
%{cmake_kf5} .. \
-DPYTHON_EXECUTABLE:PATH=%{__python3} \
-DPYTHON_INCLUDE_DIR=%{_includedir}/python%{python3_version}m \
- -DPYTHON_LIBRARY=%{_libdir}/libpython%{python3_version}m.so
+ -DPYTHON_LIBRARY=%{_libdir}/libpython%{python3_version}m.so \
+ -DBoostPython_INCLUDE_DIRS="%{_includedir}/python%{python3_version}m %{_includedir}/boost" \
+ -DBoostPython_LIBRARIES="%{_libdir}/libpython%{python3_version}m.so %{_libdir}/libboost_python%{python3_version_nodots}.so"
popd
%make_build -C %{_target_platform}
@@ -112,6 +114,7 @@ desktop-file-validate %{buildroot}%{_kf5_datadir}/applications/org.kde.%{name}.d
%changelog
* Tue Oct 29 2019 Kevin Kofler <Kevin@tigcc.ticalc.org> - 19.08.1-3
- enable Python 3 support, drop Python 2 support where it was enabled (#1738033)
+- work around BoostPython.cmake failure by setting variables explicitly
* Sat Oct 19 2019 Kevin Kofler <Kevin@tigcc.ticalc.org> - 19.08.1-2
- rebuild in Rawhide after unretirement
reply other threads:[~2026-08-04 19:44 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=178587268791.1.14834511972007957250.rpms-kig-b5b40b0190ba@fedoraproject.org \
--to=kevin@tigcc.ticalc.org \
--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