cmake linking to old libraries. Bug or feature? (was: Re: KDE/kdebase/workspace/plasma/dataengines)

[Thiago Macieira]

Andreas Pakulat wrote:
>> Then I deleted the the lib/cmake/KdepimLibs-4.3.0/ directory from my
>> KDE 4 installation and things started working without any version
>> number at all (the code before my commit). I can't explain why. But
>> this is a surprise factor and could be a bug.
>
>Not if you've read man cmake :) The find_package section explains how
> cmake finds packages if in the config-mode (the one that searches in
>lib/cmake/<package>/ for a <package>Config.cmake). It simply searches
> for <package>*/<package>Config.cmake and then runs
> <package>ConfigVersion.cmake to let the module check for version
> compatibility. If it finds a compatible one, then it takes that one.

My point is this: I had
	lib/cmake/KdepimLibs-4.2.0/
	lib/cmake/KdepimLibs-4.2.85/
	lib/cmake/KdepimLibs-4.3.0/

Like that, it doesn't build. The command-line had libakonadi-kde.so.4.2.0 
in it.

So I removed lib/cmake/KdepimLibs-4.3.0/ and then suddenly it starts 
compiling.

-- 
  Thiago Macieira  -  thiago (AT) macieira.info - thiago (AT) kde.org
    PGP/GPG: 0x6EF45358; fingerprint:
    E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
Url : http://mail.kde.org/pipermail/kde-buildsystem/attachments/20090508/2b868acb/attachment.sig