Jim Correia wrote:
> On Sep 14, 2004, at 7:04 AM, Max Bowsher wrote:
>
>> So, the next question is: Do you have a libswigpy.dylib file?
>>
>> You mentioned swig 1.3.22, didn't you?
>> In which case, the answer is certainly "no".
>>
>> Subversion isn't really compatible with swig 1.3.22 yet.
>
> I grabbed 1.3.22 because I had top pick a version. If the easiest/right
> thing to do is to step back to an older version of swig, I can do that
> (I'm only using it with subversion).
>
> What version should I be using?
1.3.22 with manually built/installed runtimes should be perfectly fine.
1.3.21 allowed the build/install of the runtimes to be accomplished with
"make runtime", "make install-runtime" whilst building swig, and most binary
packagers did exactly that.
>> - this swig version stopped building and installing the cross-module
>> runtime libraries. Subversion hasn't adapted to perform the additional
>> tasks now required of it by swig.
>
> Can I assume by your wording (yet, short term workaround) that this
> won't always be the case and using the trunk version of swig will be
> supported someday?
Yes, but most likely in the subversion 1.2.x timeframe.
Though, we will probably improve the documentation of 1.1 to indicate the
situation more clearly.
Max.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Sep 14 14:37:12 2004