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

Re: libsvn_swig_py.so not being installed

From: Max Bowsher <maxb_at_ukf.net>
Date: 2004-07-08 11:00:27 CEST

Justin Erenkrantz wrote:
> --On Wednesday, July 7, 2004 10:30 PM -0500 David Summers
> <david@summersoft.fay.ar.us> wrote:
>
>> On #svn IRC channel, breser helped me figure it out. The "make
>> install-swig-py-lib" is not being called (probably because it is not any
>> more dependent on the "make install-swig-py".
>
> install-swig-py-lib has never depended on install-swig-py. Every time I
> brought that up before, someone complained that it should be separate. So,
> this isn't recent. It'd be nice to fix it though. -- justin

I'm going to toss a very slightly related point into this discussion...

SWIG is redefining how to use it's runtime library code.
At some point in the future, we will no longer link libsvn_swig_py with -lswigpy, instead, we will run "swig -python -runtime
swigrun.i", producing a C source file, which we will then compile and link into libsvn_swig_py itself.

In other words, what I'm saying is that the distinction between the swig-py modules and the swig-py-lib will decrease, as they will
both use (at least some) swig-built source.

This means that in the future, "make swig-py" will really depend on "make swig-py-lib". I therefore think "swig-py-lib" should be
designated an internal developer convenience target (like, e.g. "make libsvn_subr"), and that "install-swig-py-lib" should be done
as part of "install-swig-py".

In summary: To build and install the complete python bindings, "make swig-py install-swig-py" should be all that is required.

Max.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jul 8 11:01:01 2004

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