[Digikam-devel] [digikam] [Bug 339180] compiler doesn't pick up libkgeomap plugin header files

RJVB rjvbertin at gmail.com
Thu Sep 18 16:33:59 BST 2014


https://bugs.kde.org/show_bug.cgi?id=339180

--- Comment #5 from RJVB <rjvbertin at gmail.com> ---
If memory serves me well, it was me who updated the Portfile for digikam 4.0.0
... O:-)

That portfile of course allowed me to do `port install digikam` without issues.
I did not use a variant for 4.0.0, I'm using +translations now. So 4.0.0 was
built using CMAKE_TYPE=releasewithdebug (which I hope equels RelWithDebInfo; I
changed that in the current Portfile).

I am a bit surprised that you can still use that old Portfile to build digikam
4.0.0, because it sets the CMAKE_MODULE_PATH to ${PREFIX}/share/cmake-2.8 ...
and MacPorts has had cmake 3.0 for a while already. (It is of course possible
that you got a binary build for the 4.0.0 version ...)

I think my assumption was right: not only did the compiler fail to find certain
header files, but it also found older versions with the result that
KGeoMapWidget::setTrackManager was undefined. When I deactivate the 4.0.0 port
(`port deactivate digikam`), the build seems to go through.

I'm curious to see what will happen on my Linux box where I also use clang-3.4
and that has digikam-4.0.0 installed (but through a PPA package so maybe the
libkgeomap headers aren't installed globally).

-- 
You are receiving this mail because:
You are the assignee for the bug.



More information about the Digikam-devel mailing list