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

Re: [Issue 1125] - Python SWIG bindings don't install correctly

From: Greg Stein <gstein_at_lyra.org>
Date: 2003-02-07 02:33:03 CET

On Thu, Feb 06, 2003 at 06:07:00PM -0500, Brandon Ehle wrote:
> I install a stock Linux distro, my python sits in /usr and doesn't
> recognize any modules in /usr/local/pythonXXX/site-packages.


> In the subversion dir, I run the following:
> ./autogen.sh && ./configure && make install && make install-swig-py-ext
> At this point would gsvn work?


The default prefix for SVN is /usr/local. So according to the scheme that I
detailed in the issue, we would not attempt to install the bindings into the
system's Python site-packages. The fallback in this case would be

If you configured and built SVN with --prefix=/usr, then the bindings
*would* be installed into Python. Or if you left the default prefix, but
passed something like --pythondir=/usr/lib/python2.2/site-packages.

I know that it would be nice to have the default simply install working
bindings. But as long as the default prefix is /usr/local, and your Python
site-packages is located in /usr, then it won't happen automatically.


p.s. note that install-swig-py-ext will be obsoleted (hopefully) soonish.
the "real" build rules are swig-py and install-swig-py. those rules work
now, but the installation part doesn't (yet) copy over the .py files and
precompile them.

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
Received on Fri Feb 7 02:29:55 2003

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