Changes to build with CMake 2.6

Andreas Pakulat apaku at
Sun Apr 27 17:02:59 UTC 2008

On 27.04.08 17:14:31, Alexander Neundorf wrote:
> On Sunday 27 April 2008, Frederik Schwarzer wrote:
> > On Sunday 27 April 2008 10:26:19 Andreas Pakulat wrote:
> > > This problem shows up if kdelibs is built with cmake 2.4, but other
> > > modules are getting built with cmake 2.6. I've posted that quite some
> > > time ago already on the buildsystem list and AFAIK the conclusion was
> > > that its not supported to do that.
> >
> > Hmm, I talked to a Debian-kde guy yesterday and he said the problem ist
> > that cmake did some implicit linking which many devs got used to.
> > However he also said that kde 4.0.68 depends on cmake 2.6, so I guess it is
> > built with 2.6. Here i have 2.6-patch 0 RC-8.
> > The concusion of the debian packagers is that they start sending patches
> > upstream to link to every needed library explicitly.
> >
> > My setup here is a packages-based KDE installation from the Debian
> > experimental archive and some apps that are compiled from source.
> If you have very current kdelibs from debian, this is the reason why it 
> doesn't work (I didn't want to say that the package is currently broken).
> They did significant modifications to the build of kdelibs, and apparently 
> they broke the build for you:
> So, build it completely from the sources and let us know if you then still 
> have problems.

But isn't it still correct that a given application/library/plugin
should list all libraries it uses symbols from. i.e. if the documentview
uses and libkdeui it should list both in its
target_link_libraries (or rather the variables for both) and not depend
on kte pulling in kdeui, right?


You will always have good luck in your personal affairs.

More information about the KDevelop-devel mailing list