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

Re: Trouble getting cvs2svn.py to work

From: Brandon Ehle <azverkan_at_yahoo.com>
Date: 2002-10-31 20:50:44 CET

>
>
>Okay, these types of changes seem like goodness. Though we need to
>change our swig.m4 to require 1.3.16, right?
>
>
Probably, typemap(in,num_inputs=0) might be supported by older versions
of swig..

>>Index: subversion/subversion/bindings/swig/svn_client.i
>>===================================================================
>>--- subversion/subversion/bindings/swig/svn_client.i (revision 3580)
>>+++ subversion/subversion/bindings/swig/svn_client.i (working copy)
>>@@ -16,7 +16,7 @@
>> * ====================================================================
>> */
>>
>>-%module _client
>>+%module client
>> %include typemaps.i
>>
>> %import apr.i
>>
>>
>
>What is the effect of these types of changes, though? Will this
>create _client.so or client.so? More accurately, will it conflict
>with the (delta|client|wc|ra|fs|repos|util).py files that sit
>alongside the .so's?
>
>
No, this affects the init_fs function name only, the _fs.so library name
comes from setup.py. It seems that the latest version of swig is
auto-prepending the _ on _fs so that you don't have to have different
module names when compiling for perl instead of python, etc.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Oct 31 20:59:16 2002

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.