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

[Friedrich W. H. Kossebau]

Am Donnerstag, 23. August 2012, 18:05:32 schrieb 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.

Thanks. But here no CMake config files should be involved, this is all from 
CMakeLists.txt files spread over the Okteta directories, as the base Kasten 
libs are still part of Okteta.

Cheers
Friedrich