On Jul 16, 2008, at 8:59 AM, Jean-Daniel Dupas wrote: Le 16 juil. 08 à 17:52, Karl Moskowski a écrit : IIRC, in Xcode 3.0, the SCM support was rewritten so it no longer spawns a task that calls the svn binary. Instead, it's linked against the Subversion API. Unfortunately, the version of the SVN libraries used is probably < 1.5.
Now you say it, I think i read it somewhere too. Anyway, it's easy to check : otool -L /Developer/Library/Xcode/Plug-ins/XcodeSubversionPlugin.xcplugin/Contents/MacOS/XcodeSubversionPlugin ... /usr/lib/libsvn_fs_fs-1.0.dylib (compatibility version 1.0.0, current version 1.0.0) /usr/lib/libsvn_fs-1.0.dylib (compatibility version 1.0.0, current version 1.0.0) /usr/lib/libsvn_ra_dav-1.0.dylib (compatibility version 1.0.0, current version 1.0.0) /usr/lib/libsvn_ra_local-1.0.dylib (compatibility version 1.0.0, current version 1.0.0) ...
Has anyone tried installing Subversion 1.5 overtop of 1.4? Or deleting 1.4, and then installing 1.5?
The Xcode Subversion plugin does indeed use the Subversion client libraries, but Subversion 1.5 should install new versions of those client libraries, which will then be used by the Xcode Subversion plugin.
This doesn't help people who want, for example, to use 1.4 for some projects, and 1.5 for others, but at least it should be possible to use Subversion 1.5 and Xcode 3.* in some fashion.
One issue is that, in that list of dynamic libraries that the Xcode Subversion plugin links against, there is a library that was renamed from 1.4 to 1.5 (and isn't public anyway, and so shouldn't have been linked against):
/usr/lib/libsvn_ra_dav-1.0.dylib
So if you try to uninstall 1.4, and install 1.5, and you find that the Xcode IDE fails to load its Subversion plugin correctly because it can't find that library, this should help:
sudo ln -s /usr/lib/libsvn_ra_neon-1.dylib /usr/lib/libsvn_ra_dav-1.0.dylib
-- Andrew |