From 7d2d0670b6e52d7bf3c9f626770b5204e0423bc9 Mon Sep 17 00:00:00 2001 From: Adriaan de Groot Date: Mon, 27 Aug 2007 13:58:19 +0000 Subject: [PATCH] Actually, forcing a particular STL implementation on the C bindings is a bad idea. git-svn-id: svn://anonsvn.kde.org/home/kde/trunk/kdesupport/taglib@705222 283d02a7-25f6-0310-bc7c-ecb5cbfe19da --- bindings/c/CMakeLists.txt | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/bindings/c/CMakeLists.txt b/bindings/c/CMakeLists.txt index 6f156714..629c7ef2 100644 --- a/bindings/c/CMakeLists.txt +++ b/bindings/c/CMakeLists.txt @@ -26,7 +26,14 @@ TARGET_LINK_LIBRARIES(tag_c tag ) # using these bindings. CHECK_LIBRARY_EXISTS(Crun __RTTI___ "" HAVE_CRUN_LIB) IF(HAVE_CRUN_LIB) - TARGET_LINK_LIBRARIES(tag_c Cstd Crun) + # Which libraries to link depends critically on which + # STL version is going to be used by your application + # and which runtime is in use. While Crun is pretty much + # the only game in town, the three available STLs -- Cstd, + # stlport4 and stdcxx -- make this a mess. We really only + # support stdcxx, but won't force the issue here. + # + # TARGET_LINK_LIBRARIES(tag_c Cstd Crun) ENDIF(HAVE_CRUN_LIB) SET_TARGET_PROPERTIES(tag_c PROPERTIES VERSION 0.0.0 SOVERSION 0 )