Bug 294510

Summary:	Unclear compiling error description in kde-baseapps because of missing libstreamanalyzer-dev
Product:	[Developer tools] buildsystem	Reporter:	firen <firen2k5>
Component:	KDE4 (cmake)	Assignee:	Alexander Neundorf <neundorf>
Status:	REPORTED ---
Severity:	wishlist	CC:	cfeck
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Compiled Sources
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description firen 2012-02-20 17:24:53 UTC

Version:           Git (using Devel) 
OS:                Linux

Unclear compiling error description in kde-baseapps because of missing libstreamanalyzer-dev

Reproducible: Didn't try


Actual Results:  
While trying to compile kde-baseapps I got following error:

- Found Qt-Version 4.7.4 (using /usr/bin/qmake) -- Found X11: /usr/lib/x86_64-linux-gnu/libX11.so -- Found KDE 4.7 include dir: /usr/include -- Found KDE 4.7 library dir: /usr/lib -- Found the KDE4 kconfig_compiler preprocessor: /usr/bin/kconfig_compiler -- Found automoc4: /usr/bin/automoc4 CMake Error at /usr/share/kde4/apps/cmake/modules/FindPackageHandleStandardArgs.cmake:198 (MESSAGE): Couldn't find Strigi streams and streamanalyzer libraries. Set the environment variable STRIGI_HOME (or CMAKE_PREFIX_PATH if using CMake

=2.6) to the strigi install dir. (missing: STRIGI_STREAMS_LIBRARY STRIGI_STREAMANALYZER_LIBRARY STRIGI_INCLUDE_DIR) Call Stack (most recent call first):
/usr/share/kde4/apps/cmake/modules/FindStrigi.cmake:105 (find_package_handle_standard_args) CMakeLists.txt:10 (find_package)

-- Configuring incomplete, errors occurred!


Expected Results:  
Maybe it would be a good idea to add that it would fix a problem installing libstreamanalyzer-dev package?

Comment 1 Jekyll Wu 2013-01-01 12:56:58 UTC

I think "Couldn't find Strigi streams and streamanalyzer libraries." is already clear enough. 

Also, libstreamanalyzer-dev  is just a downstream (Debian) specific package name.

Comment 2 Justin Zobel 2021-03-09 05:27:13 UTC

Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.