Hi Michael,
at least for Windows it does make sense to link dynamically and to be
prepared for the case that the library is not present.
You may not have a static lib at hand and compiling it by yourself may
be too much effort or too compilicated.
For that reason, QLGT for Windows was delivered without libexif until I
simply copied the precompiled .dll from a binary GIMP distribution.
Regards,
Helmut
Am 2011/09/14 23:12, schrieb Michael Klein:
> Hi,
>
> QLGT is linked with libexif.{so,dylib,dll}, yet the exif functions are
> resolved manually in CWptDB.cpp with QLibrary::resolve("libexif", ...).
>
> Does that make any sense? The manual resolve doesn't work on OS X
> unless libexif.dylib is copied/symlinked to the application bundle,
> because QLibrary doesn't search the standard library paths.
>
> Regards,
> Michael
>
------------------------------------------------------------------------------
Doing More with Less: The Next Generation Virtual Desktop
What are the key obstacles that have prevented many mid-market businesses
from deploying virtual desktops? How do next-generation virtual desktops
provide companies an easier-to-deploy, easier-to-manage and more affordable
virtual desktop model.http://www.accelacomm.com/jaw/sfnl/114/51426474/
_______________________________________________
Qlandkartegt-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qlandkartegt-users
