Bug 203144 - ruby bindings for nepomuk and soprano don't compile if cmake is called with -DBUILD_smoke=OFF
Summary: ruby bindings for nepomuk and soprano don't compile if cmake is called with -...
Status: RESOLVED UNMAINTAINED
Alias: None
Product: bindings
Classification: Developer tools
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: kde-bindings
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2009-08-09 10:04 UTC by Stefano Crocco
Modified: 2018-09-26 04:09 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:

Attachments
patch to make nepomuk build (791 bytes, patch)
2009-08-09 10:06 UTC, Stefano Crocco 		Details
patch to make soprano build (825 bytes, patch)
2009-08-09 10:07 UTC, Stefano Crocco 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Stefano Crocco 2009-08-09 10:04:47 UTC 
Version:            (using Devel)
OS:                Linux
Installed from:    Compiled sources

Attempting to compile the nepomuk or soprano ruby bindings fails at linking stage if cmake is called with -DBUILD_smoke=OFF (of course, I do have smoke installed. I just want to compile it separately from the ruby bindings). The reason seems to be that some needed libraries aren't given to the linker. In particular, they're the soprano libraries for soprano and the soprano and qt core libraries for nepomuk. If -DBUILD_smoke=OFF isn't passed to cmake, but smoke building is later disabled using ccmake, everything builds correctly.
Comment 1 Stefano Crocco 2009-08-09 10:06:35 UTC 
Created attachment 36005 [details]
patch to make nepomuk build
Comment 2 Stefano Crocco 2009-08-09 10:07:07 UTC 
Created attachment 36006 [details]
patch to make soprano build
Comment 3 Andrew Crouthamel 2018-09-26 04:09:46 UTC 
Hi there, this bug has been identified to be related to nepomuk, the semantic searching system in prior versions of KDE. Please note that nepomuk has been replaced by Baloo. I'm going to close this bug due to the use of the new Baloo system. Please do file a new bug for frameworks-baloo if you happen to continue having issues with search.