[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: Branko ─îibej <brane_at_xbc.nu>
Date: 2004-07-08 13:44:03 CEST

Max Bowsher wrote:

>Russell Yanofsky wrote:
>>Max Bowsher wrote:
>>>I'm going to toss a very slightly related point into this
>>>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.
>>The "install-swig-py-lib" doesn't install the swig runtime -- we assume unix
>>users already have that installed. It installs our python utility library
>>(subversion/bindings/swig/python/libsvn_swig_py) which hold some common
>>functions used by all the python modules.
>Yes. I agree with all you say above. My point is that future versions of swig will *NOT* install a swig runtime library. Instead,
>swig users will be expected to run a swig command generating a .c file which they compile and link into a library of their own,
>which provides the swig runtime features. In our case, it seems to make the most sense to integrate this into the existing
Note that we already do this on Windows, even with SWIG-1.3.19. We can
easily adapt the logic for Unix (it's infact quite portable).

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

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.