FindKdepimLibs.cmake

[Christian Ehrlicher]

Von: Allen Winter <winter at kde.org>
> On Wednesday 30 May 2007 5:56:05 am Aaron J. Seigo wrote:
> > 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?
> > 
> 
> I don't believe that any libs in kdelibs nor kdepimlibs should be
> optionally built.
> We need to either 1) make boost a hard dependency or 2) copy parts of
> boost
> into kdepimlibs or 3) ??
> 
Syndication was made optional because I wanted to build kdepimlibs without boost on win32 at this time. We needed some time to get some (working) boost headers. As we now have them, it can get a hard dependency.

Christian

-- 
Psssst! Schon vom neuen GMX MultiMessenger gehört?
Der kanns mit allen: http://www.gmx.net/de/go/multimessenger