Problems with svncpp, what to do?
aleixpol at gmail.com
Wed Apr 2 23:32:42 UTC 2008
I think that you should only let it compile if the user has the proper version.
If you don't want to make the finder so intelligent, maybe you could
just add the option() and don't compile it by default since we are not
On 4/3/08, Andreas Pakulat <apaku at gmx.de> wrote:
> On 02.04.08 23:55:10, Andreas Pakulat wrote:
> > Hi,
> > Matt told me today that subversion support doesn't build for him. The
> > reason is that he's using svncpp (rapidsvn C++ client lib) 0.9.6, while
> > I used 0.9.4 while working on svn support. I also had that version
> > installed until today (did an upgrade). Apparently the rapidsvn devs
> > don't have any binary compatibility - or even source compat - policy and
> > simply reworked large parts of the API.
> > I'm not sure what to do now, unfortunately there's no way to do a
> > version check (as far as I can see), because they didn't feel like
> > increasing the SOVERSION of the library and there's also no header with
> > version information. 0.9.6 is relatively new, so I don't want to
> > introduce a dependency on it and thus keep everybody else out...
> > Any ideas?
> One option (though I don't like it) would be reading the client.hpp and
> check for one of the now-missing methods and set a define based on that.
> That could then be used in the code to activate the path for <=0.9.4 or
> So you're back... about time...
> KDevelop-devel mailing list
> KDevelop-devel at kdevelop.org
More information about the KDevelop-devel