Notice: taglib-extras required
Jeff Mitchell
mitchell at kde.org
Sat Mar 21 12:33:53 UTC 2009
Andreas Pakulat wrote:
> Are the errors about libraries that taglib-extras links against or from
> amarok code missing taglib-extras?
The issue is when libraries that link to amaroklib are themselves being
linked. These libraries do not use taglib-extras directly, but
amaroklib does, and when amaroklib is being linked in, it spawns the
linking errors.
> Usually KDE apps automatically set
> rpath on their binary (because FindKDE4Internal.cmake sets a cmake flag
> to always use rpath), so the export above shouldn't be necessary as long
> as CMake knows the proper absolute path to the taglib-extras library
> when building amarok.
CMake does know the proper absolute path -- I've done some debugging
with Mark. However, there is a catch -- the collectionscanner is built
separately and has no kdelibs deps (but depends on taglib-extras) so
FindKDE4Internal.cmake is not run in this case. (Try running cmake with
-DWITH_PLAYER=Off ... but this might not be an issue, since the
collection scanner links directly with taglib-extras, not this
roundabout lining causing the errors that Mark and a few others are seeing).
> I'm currently rebuilding all of kde4 so should see this soon myself as
> well. At least I can't see any obvious errors from a quick look through
> amarok's CMakeLists.txt or the FindTagLib-Extras.cmake module.
We can't either. But please let us know if you hit this error or not,
and if so, if you know how to fix it.
Thanks,
Jeff
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 260 bytes
Desc: OpenPGP digital signature
URL: <http://mail.kde.org/pipermail/amarok/attachments/20090321/a74cec8e/attachment.sig>
More information about the Amarok
mailing list