Brandon Ehle <azverkan@yahoo.com> writes:
> I ran into the same problem with the newest version of swig. Try this
> patch.
>
> Index: subversion/subversion/bindings/swig/apr.i
> ===================================================================
> --- subversion/subversion/bindings/swig/apr.i (revision 3580)
> +++ subversion/subversion/bindings/swig/apr.i (working copy)
> @@ -56,7 +56,7 @@
> %apply long long { apr_time_t };
>
> /* 'apr_time_t *' will always be an OUTPUT parameter */
> -%typemap(ignore) apr_time_t * (apr_time_t temp) {
> +%typemap(in,num_inputs=0) apr_time_t * (apr_time_t temp) {
> $1 = &temp;
> }
Okay, these types of changes seem like goodness. Though we need to
change our swig.m4 to require 1.3.16, right?
> 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?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Oct 31 19:29:55 2002