| Summary: | Provide a list of CMake configuration options. | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Andrzej <superandrzej> |
| Component: | Documentation | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | caulier.gilles, mike |
| Priority: | NOR | ||
| Version: | 2.1.1 | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | 8.0.0 | |
| Sentry Crash Report: | |||
|
Description
Andrzej
2011-09-26 21:34:24 UTC
Already done in README file : https://projects.kde.org/projects/extragear/graphics/digikam/repository/revisions/master/entry/README#L115 Gilles Caulier 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. 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... 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. No, it's not possible to play with OpenCV config from digiKam compilation setup. Gilles Caulier 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. (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 Thank you for the info. I guess that the same story is with opencv and libkface Andrzej List of cmake compilation options is given online here : https://www.digikam.org/api/index.html#cmakeoptions |