Re: SWIG Python bindings (more OpenBSD badness)

On Sat, Mar 29, 2003 at 09:31:42PM -0500, Mark G wrote:
>...
> When I compiled Subversion I did a:
>
> make swig-py

You also need:

$ make install-swig-py

>...
> In /disk/0/subversion/run/lib:
> -rw-r--r-- 1 svn devel 70036 Mar 29 20:13 libsvn_swig_py-1.a
> -rwxr-xr-x 1 svn devel 1025 Mar 29 20:13 libsvn_swig_py-1.la
> -rwxr-xr-x 1 svn devel 76763 Mar 29 20:13 libsvn_swig_py-1.so.0.0

Those are just support libraries. The "real" bindings need to be installed.
By default, they'll go into /disk/0/subversion/run/lib/svn-python. You will
then want to do one of two things:

1) adjust your Python path so the new package can be found:

 $ PYTHONPATH=/disk/0/subversion/run/lib/svn-python

2) symlink from your Python installation to the SVN installation:

 $ cd /usr/lib/python2.2/site-packages
 $ ln -s /disk/0/subversion/run/lib/svn-python/svn svn

Personally, I use the latter since it is tough to ensure that everybody
will get the environment variable set. I haven't tested it, but you might
also be able to do:

$ make swig_pydir=/usr/lib/python2.2/site-packages/svn install

Cheers,
-g

-- 
Greg Stein, http://www.lyra.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org