Bug 360822 - cmake does not find Boost Python support
Summary: cmake does not find Boost Python support
Status: RESOLVED FIXED
Alias: None
Product: kig
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: David E. Narvaez
URL:
Keywords:
: 363716 (view as bug list)
Depends on:
Blocks:
 
Reported: 2016-03-21 16:56 UTC by Maurizio Paolini
Modified: 2017-02-13 12:32 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Maurizio Paolini 2016-03-21 16:56:17 UTC
after a fresh "git clone git@git.kde.org:kig", cmake is not finding the optional BoostPython
package.  It turns out that the compilation problem that confuses "cmake" goes away by adding the option -fexceptions.
One possible solution is suggested in the review request
https://git.reviewboard.kde.org/r/127450/

Probably due to caching, I did not experience the problem on my usual working copy.

Reproducible: Always

Steps to Reproduce:
1. git clone git@git.kde.org:kig
2. cd kig
3. cmake -DCMAKE_INSTALL_PREFIX=/usr -DKDE_INSTALL_SYSCONFDIR=/etc -DKDE_INSTALL_QTPLUGINDIR=lib/qt5/plugins $(pwd -P)



Actual Results:  
cmake did not find the optional Boost Python package

Expected Results:  
Boost Python package should be found, having all the required devel packages


https://git.reviewboard.kde.org/r/127450/
Comment 1 Luigi Toscano 2017-02-12 23:20:42 UTC
I think that this was solved long time ago (Applications 16.04).
See the review in the bug Description and the following commits:
https://commits.kde.org/kig/96526f6d20e7abc9ec2c1de33e911e4329d07f76
https://commits.kde.org/kig/3c7c17c8abb0dc99c293bb45252126cc058344a2
Comment 2 Luigi Toscano 2017-02-12 23:21:00 UTC
*** Bug 363716 has been marked as a duplicate of this bug. ***
Comment 3 Maurizio Paolini 2017-02-13 12:32:37 UTC
(In reply to Luigi Toscano from comment #1)
> I think that this was solved long time ago (Applications 16.04).
> See the review in the bug Description and the following commits:
> https://commits.kde.org/kig/96526f6d20e7abc9ec2c1de33e911e4329d07f76
> https://commits.kde.org/kig/3c7c17c8abb0dc99c293bb45252126cc058344a2

The problem seems indeed solved.  Thank you!