On 01/10/05 09:46:59, John Peacock wrote:
> Max Bowsher wrote:
>
>> Kouhei Sutou wrote:
>>
>>> I want to require SWIG 1.3.22 or later.
>>> Because Ruby module of SWIG 1.3.21 has a bug. It's a %import
>>> handling(*).
>>
>>
>> That's a little difficult, since the perl/python bindings currently
>> require 1.3.19 to 1.3.21, no later or earlier.
>
> And the additional difficulty that SWIG 1.3.22 changed the build process
> such that the runtime libraries are no longer available (i.e. the targets
> don't exist in the SWIG Makefile). Any project intending to use SWIG
> runtime libraries must build them manually.
Wrong, there are no more runtime libraries. Gone.
> Subversion has not added
> code to do that; there was a discussion with one of the SWIG developers
> to change how Subversion worked wrt SWIG, but I believe that was shot
> down because it would orphan all existing installations.
Well, the reason I stopped is because I don't know enough about the
internal build process of subversion to get SWIG working to the
satisfaction of the devs, but at least from the SWIG side of the fence the
patches I posted work fine. I was getting a bunch of errors about
mixmatched subversion versions and whatnot. Someone with a little more
knowledge subversion needs to step up to the plate, and I am willing to
help them. Or when I get around to it I will probably try and learn more.
John
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jan 13 03:14:03 2005