strigi is split into multiple KDE git modules (as per http://www.kdedevelopers.org/node/4190\). Although the justification was to allow e.g. Tracker to be able to use libstreams without the rest of Strigi, Strigi doesn't seem to build without the best "strigi.git" supermodule.
Specifically, merely attempting to build e.g. strigiclient by itself does not pick up the SOVERSION correctly, so you end up with libraries such as libfoo.so.SOVERSION instead of libfoo.so.4. This can be fixed by adding a find_package(strigi) to the CMakeLists.txt for strigiclient.
However, this isn't a fix for all 5 modules, as strigiconfig.cmake is provided by libstreams, but libstreams itself depends on libstrigiclient (i.e. there an inter-module dependency going on).
It would be outstanding to have all 5 submodules able to be built independently, with non-cyclic dependencies on each other (for instance kdesrc-build simply hacks around the problem by having strigi's CMake download and build the rest -- but this ignores the normal CMake options in use by kdesrc-build users). This would also allow e.g. Tracker to be able to refer only to the 2 or 3 tarballs out of 5 that they really need.
Thanks. (as an aside I am reporting this bug which was initially noted by kdepepo on #kde-devel, with further troubleshooting done by Michael Jansen, author of "build-tool")
Log in to post a comment.