[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

libsvn_swig_* libraries

From: Sviatoslav Sviridov <svd_at_altlinux.ru>
Date: 2006-03-20 19:29:52 CET

Hello,

I'd like to ask what libsvn_swig_* libraries are? Are they intended to
be used _only_ from corresponding swig bindings or are there possible
usage scenarios from other libraries/programs?

I'm trying to build update subversion package for ALT Linux and I'm
working now on subversion-1.3.1.
The problem is that libsvn_swig_* libraries contain undefined symbols
(from lib{python,ruby,perl}), but our packaging policy disallows to have
undefined symbols for libraries that are located in publicly accessible
places.
These undefined symbols do not cause a problem during runtime because
they are called from corresponding interpreter, so all required symbols
are already resolved. BTW, libsvn_swig_perl-1.so.0 uses also one symbol
from /usr/lib/perl5/vendor_perl/i386-linux/auto/SVN/_Core/_Core.so. It
is svn_swig_pl_get_current_pool, which is probably better to move to
library.

From my side I have several solutions:
1. (preffered) Install libsvn_swig_* libraries somewhere into
/usr/lib/libsvn_swig/ and use RPATH for building swig bindings
2. Link libsvn_swig_* with required libraries. However, libsvn_swig_perl
and _Core.so will have cycle dependency.

So, my question is: is it safe to install libsvn_swig_* into other
folder that /usr/lib? (I guess it is true if these libraries will be
used only from swig bindings).

-- 
Best Regards,
Sviatoslav Sviridov

Received on Mon Mar 20 19:30:22 2006

This is an archived mail posted to the Subversion Dev mailing list.