FindKdepimLibs.cmake

Aaron J. Seigo aseigo at kde.org
Wed May 30 10:56:05 BST 2007


hi..

the FindKdepimLibs.cmake module in kdelibs/cmake/modules/ assumes that 
libsyndication from kdepimlibs will be built if kdepimlibs exists; or at 
least it unconditionally sets KDE4_SYNDICATION_LIBS. however, libsyndication 
is an option component of kdepimlibs depending on whether or not Boost is 
available on the system at build time.

i assumed that libsyndication not being there would result in 
KDE4_SYNDICATION_LIBS not being set, but this evidently isn't the case and 
has, in turn, created an unintentional hard dependency on Boost in kdebase 
(workspace/plasma/engines/cia.vc, to be exact). i don't particularly like 
this, and figure the solution is to deal with KDE4_SYNDICATION_LIBS properly 
in FindKdepimLibs.cmake.

however, i'm not sure how to implement this in FindKdepimLibs in the most 
appropriate fashion and am hoping a cmake guru might be able to offer some 
insight. my guess is that a find_library(KDE4_SYNDICATION_LIBRARY NAMES 
syndication) is what is necessary, followed by a call to see if 
${KDE4_SYNDICATION_LIBRARY} gets set (meaning that libsyndication is there) 
and then based on that setting KDE4_SYNDICATION_LIBS.

is that the right approach, is there a better/preferred mechanism?

-- 
Aaron J. Seigo
humru othro a kohnu se
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43

Full time KDE developer sponsored by Trolltech (http://www.trolltech.com)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20070530/773e52c3/attachment.sig>


More information about the kde-core-devel mailing list