Bug 282869 - Provide a list of CMake configuration options.
Summary: Provide a list of CMake configuration options.
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Documentation (show other bugs)
Version: 2.1.1
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-26 21:34 UTC by Andrzej
Modified: 2022-12-24 12:28 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In: 8.0.0
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andrzej 2011-09-26 21:34:24 UTC
Version:           2.1.1 (using KDE 4.7.1) 
OS:                Linux

I really miss a place where all cmake configuration options are listed.
something similar to ./confiugre --help

It might be a text file in source packages or a html page in digikam.org.
Sometimes there is a need to disable some dependencies or functionalities but I cannot find how to do it or even whether it is possible.

For example in my case I can compile digikam but when I start it I receive a message: "Illegal instruction"

Deducting from other bugs it seems to be the problem with opencv.
But I don't know how to get rid off opencv dependency.
As a result I cannot use digikam at all

Reproducible: Always

Steps to Reproduce:
Search digikam.org or sources for this information


Expected Results:  
text file in source packages or a html page in digikam.org with all cmake configuration options
Comment 1 caulier.gilles 2011-09-27 09:02:30 UTC
Already done in README file :

https://projects.kde.org/projects/extragear/graphics/digikam/repository/revisions/master/entry/README#L115

Gilles Caulier
Comment 2 Andrzej 2011-10-06 22:26:20 UTC
Thank you for the info.
I probably have seen this file but my impression was that these are just examples and not a complete list.
I was hoping that there is a was a way to disable some kipi-plugins or some dependencies like opencv or marble that are not necessary for very one.

BTW.
I've found few mistakes/ discrepancies  in README files of Digikam and of Kipi-plugins. I will create separate bug reports.

I had problems with opencv because it was imposing during configuration sse2 instructions that are not supported by my Athlon processor and digikam was not even starting. (it took me some time to discover it)
So my suggestion would be to either introduce an option to disable openCV or put an information that in case of "illegal instruction" message, openCV should be configured with 
-DENABLE_SSE2=OFF
cmake option.
Comment 3 caulier.gilles 2011-10-07 07:51:30 UTC
For opencv, it's a compilation time switch which can be used only with OpenCV package. We cannot control it through digiKam compilation. Report this problem to OpenCV team...
Comment 4 Andrzej 2011-10-07 23:15:00 UTC
Yes I know that this particular problem is on OpenCV side but I was wondering if it would be possible to get rid of this dependency during cmake configuration in case there is a need to do so.
Comment 5 caulier.gilles 2011-10-08 11:27:22 UTC
No, it's not possible to play with OpenCV config from digiKam compilation setup.

Gilles Caulier
Comment 6 Andrzej 2011-10-08 20:41:51 UTC
I'm sorry.

My wording was not precise enough:
I wanted to know if it was possible to compile digiKam without OpenCV or without Marble.

These dependencies are as big as digiKam itself but some people may not need functionalities these dependencies provide. And in some cases these dependencies may be troublesome.
Comment 7 Michael G. Hansen 2011-10-08 21:34:44 UTC
(In reply to comment #6)
> My wording was not precise enough:
> I wanted to know if it was possible to compile digiKam without OpenCV or
> without Marble.
> 
> These dependencies are as big as digiKam itself but some people may not need
> functionalities these dependencies provide. And in some cases these
> dependencies may be troublesome.

Currently there is no way to compile digikam without marble, which is required by libkgeomap. Separating marble out of libkgeomap would lead to a bunch of code-duplication in terms of geo-related code. Also, making libkgeomap optional in digikam is a lot of work and requires a lot of test-compilation to make sure it actually works.

Michael
Comment 8 Andrzej 2011-10-15 19:34:04 UTC
Thank you for the info.
I guess that the same story is with opencv and libkface

Andrzej
Comment 9 caulier.gilles 2022-12-24 12:28:13 UTC
List of cmake compilation options is given online here :

https://www.digikam.org/api/index.html#cmakeoptions