internal lib name vs. output lib name, getting internal dependencies?

[Michael Pyne]

On Thursday, August 23, 2012 23:58:22 Friedrich W. H. Kossebau wrote:
> When proposing solutions, please keep in mind that I try to keep the
> different modules as independent as possible, so moving things
> around/outside will not need big changes in the build system.

First off, keep in mind that I have about 0 insight into the issue even after 
your detailed mail.

With that said, if this is an issue with library names changing, have you 
ensured that there are not any old CMake config files hanging out (I think 
they're normally in $KDEDIRS/share/apps/cmake/modules)?

I've had issues with old config files being found and referencing old versions 
of libraries which I've since deleted, and having that cause build failure. 
Might be the same thing here.

Regards,
 - Michael Pyne
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-buildsystem/attachments/20120823/b3bfa162/attachment.sig>