Summary: | Digikam configure script misleading. | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | Evert Vorster <evorster> |
Component: | Portability-Cmake | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED NOT A BUG | ||
Severity: | normal | CC: | caulier.gilles |
Priority: | NOR | ||
Version: | 1.3.0 | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 7.6.0 | |
Sentry Crash Report: |
Description
Evert Vorster
2010-06-21 21:01:26 UTC
We cannot do much about this because the pkgconfig macro from cmake simply says whether it has found a suitable version or not. If not, it does not tell which version was found but wasn't sufficient. Thanks for the extra info. I was under the impression that each project can fine-tune their own cmake script, same as the configure script of old. Do you think we can ask for a change in the cmake scripts themselves, then? -Evert- We could do a workaround, first requesting every version of the library and then in a second step the desired version. But I do not think it's worth the work. Actually I think it would be better if kde would switch to the new cmake pkgconfig wrapper. This one gives much better console output of what's exactly requested. Nope. I prefer to keep things simple as well. It would be better for the pkgconfig wrapper to be used in KDE. |