Bug 493280 - Calligra 4.0.1 source code: cmake cannot successfully configure soprano (RDF feature)
Summary: Calligra 4.0.1 source code: cmake cannot successfully configure soprano (RDF ...
Status: RESOLVED NOT A BUG
Alias: None
Product: calligracommon
Classification: Applications
Component: general (other bugs)
Version First Reported In: 4.0.1
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Calligra Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-09-17 16:40 UTC by Jens Radloff
Modified: 2024-09-22 18:24 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jens Radloff 2024-09-17 16:40:32 UTC
There is no soprano/rdf package in my Tuxedo OS 3 installation which I could install from its package repositories. Tuxedo OS 3 is based on Ubuntu 22.04.*. Here is some information about this Linux distribution:

https://www.tuxedocomputers.com/en/Infos/Help-Support/Frequently-asked-questions/What-is-the-differences-between-TUXEDO-OS-and-Ubuntu/Kubuntu-_1.tuxedo

When I configure the Calligra source code in version 4.0.1 for its compilation using cmake, then the cmake command returns the following information at the end of the configuration process:

------ The following product(set)s/features can NOT be built ------
-- FEATURE_RDF:  RDF feature  |  Soprano not found
-- PART_QTQUICK:  QtQuick Plugin that provides Calligra components  |  Not yet ported to Qt5/KF5
-- PLUGIN_SEMANTICITEMS:  Semantic items plugins  |  Required internal dependency missing: FEATURE_RDF
-- DEVEL_HEADERS:  Headers of libraries  |  Not yet ported to Qt5/KF5

But after that the output of the configuration process run by cmake indicates that in the next step I could start compiling the Calligra source code.

I tried to fullfill the RDF/soprano dependency for getting the Calligra source code successfully configured so that Calligra could make use of the RDF feature provided by soprano, but I was not successful in this respect.

Due to this I am issuing this bug report.

When I tried to get soprano compiled on my machine I oriented myself on the instructions at

https://www.linuxfromscratch.org/blfs/view/7.5/server/soprano.html

The patch file specified there can be downloaded here:

https://www.linuxfromscratch.org/patches/downloads/soprano/soprano-2.9.4-dbus-1.patch

I tried to configure the soprano source code using the following cmake command:

$ cmake .. --fresh -DCMAKE_INSTALL_PREFIX=/opt/soprano/soprano-2.9.4/bin -DCMAKE_BUILD_TYPE=Release -Wno-dev \
-D CMAKE_MODULE_PATH=/usr/share/cmake-3.30/Modules:/usr/lib/x86_64-linux-gnu/cmake/Qt6:/usr/lib/x86_64-linux-gnu/qt6/qml/org/kde/i18n/localeData

But I did not manage to successfully configure the soprano source code for its generally working compilation. Even not by changing the contents of single files within the source code by for example commenting certain lines in them.

The soprano libraries are so old, I  ask myself if they are still required by Calligra 4.0.1 - could it be that due to this all referrers to soprano in the Calligra source code in version 4.0.1 could be removed?

Or do you have a solution for the missing soprano functionality in my Tuxedo OS 3 installation?

SOFTWARE/OS VERSIONS:
Linux/KDE Plasma:  Tuxedo OS 3
KDE Plasma Version:  6
KDE Frameworks Version: 0.3.0 *
Qt Version: 6.7.2

* I think this version number is wrong. I will check it again, but I need to reboot my machine for this, I will be back here soon to correct this version number, if necessary.
Comment 1 Jens Radloff 2024-09-17 16:59:16 UTC
Correct information about installed KDE Frameworks Version:

KDE Framework Integration (kf6-frameworkintegration) version: 6.5.0
Comment 2 Jens Radloff 2024-09-22 18:24:36 UTC
Today I compiled what I downloaded about 10 days ago as the current Calligra source code by using git. Having compiled this source code it appeared that I have compiled a Calligra version which is 2 years old, i.e. version 3.2.1.

Thus this bug report here is not applicable considering the fact that a very recent and new version of Calligra is available (4.0.1), but not via git, as I had to notice today, although I successfully could apply the command "git reset --hard 4.0.1" in my git directory on my local machine.

So this bug report refers to an 2 years old version of Calligra, so the behavior I reported here must be considered as not being a bug. Due to this, I will close this bug report now.