summaryrefslogtreecommitdiffstats
path: root/src/imageplugins/coreplugin/sharpnesseditor/matrix.cpp
diff options
context:
space:
mode:
authorMichele Calgaro <michele.calgaro@yahoo.it>2025-05-03 22:45:33 +0900
committerMichele Calgaro <michele.calgaro@yahoo.it>2025-05-06 17:48:11 +0900
commit0254a5942b7ff18bf0072db3ebcd591512d99a10 (patch)
treedba05baf76c79adfea4cdf039313b3fd41f334da /src/imageplugins/coreplugin/sharpnesseditor/matrix.cpp
parentbbb36b6c0fa49b03c1f3e08b38df81ce3bce4d48 (diff)
downloaddigikam-0254a5942b7ff18bf0072db3ebcd591512d99a10.tar.gz
digikam-0254a5942b7ff18bf0072db3ebcd591512d99a10.zip
Fix showfoto usability.
This resolves issue #50. The problem seems to be a known issue already addressed by the original authors. This is an extract from the 'ChangeLog' file that best describes the issue: ``` Fix a linking problem with showfoto, image plugins and --enable-gcc-hidden-visibility: All image plugins link to libdigikam.so. The showfoto executable however does not link to this lib, but statically links the relevant parts. With visibility hidden, now the linker obviously cannot see the already linked DImgInterface class, and there would be two different static variables for DImgInterface::instance(). One with the loaded image, the other (from the image plugins) with a null image. ``` Linking against libdigikam.so instead of including the libraries in a static way solves the issue. Signed-off-by: Michele Calgaro <michele.calgaro@yahoo.it> (cherry picked from commit f8074c05d9a2ad3b4a4e44557222ad51539b7e79)
Diffstat (limited to 'src/imageplugins/coreplugin/sharpnesseditor/matrix.cpp')
0 files changed, 0 insertions, 0 deletions