| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Signed-off-by: Slávek Banko <slavek.banko@axis.cz>
(cherry picked from commit 67d18a6d8e8b76c9d805c2665779a2c9c5dab88b)
|
|
|
|
|
| |
Signed-off-by: Michele Calgaro <michele.calgaro@yahoo.it>
(cherry picked from commit a2ab145c9a7b83a42fc168a07972f0de3e31efef)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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)
|
|
|
|
|
| |
Signed-off-by: Michele Calgaro <michele.calgaro@yahoo.it>
(cherry picked from commit 76a8e935be38afad0105c46d5a2aa7b58162223b)
|
|
Signed-off-by: Michele Calgaro <michele.calgaro@yahoo.it>
(cherry picked from commit ee0d99607c14cb63d3ebdb3a970b508949fa8219)
|