Re: [PATCH] Encourage users to upgrade to SWIG 1.3.24

On 8/4/05, Max Bowsher <maxb@ukf.net> wrote:
> I _know_ I've had a working python bindings set using SWIG 1.3.21 and
> *--disable-static* in the past.
Perhaps the requirements of the Subversion build have changed?

If I build SWIG 1.3.21 without the "--enable-static" flag, it does not
install "libswigpy.a". On my machine, with default configure settings,
Subversion needs "libswigpy.a" to build. Newer versions of SWIG do not
exhibit this problem.

In many cases, users have a different version of SWIG already
installed on their machine which has "libswigpy.a". If users do not
use the --enable-static flag, then Subversion will skip over the new
version of SWIG that they just installed (because it didn't install
libswigpy.a), and use the older version of libswigpy.a instead. I
experienced this problem on my system.

There are also more severe issues with Subversion's support for SWIG
1.3.20 and 1.3.21, which have not yet been addressed. See <
http://svn.haxx.se/dev/archive-2005-08/0053.shtml >. For this reason,
I think it would be a good idea to encourage users to upgrade to newer
versions of SWIG, if they can.

Cheers,

David

-- 
David James -- http://www.cs.toronto.edu/~james
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org