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

diff --git a/bindings/c/CMakeLists.txt b/bindings/c/CMakeLists.txt
index 6f156714da8011a2eeef75394ad363880e87d1d0..629c7ef27334aa79663decb9e2ed9600a8ca9316 100644 (file)
--- 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 )