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

Re: Bugs in Subversion's SWIG 1.3.21 support

From: John Lenz <lenz_at_cs.wisc.edu>
Date: 2005-08-06 21:27:46 CEST

On Fri, August 5, 2005 8:27 am, David James said:
> This would be a huge improvement! I'm eager to get the latest bug
> fixes and improvements from the SWIG team, but I don't want to add
> 1.3.25 as a dependency. If we can treat SWIG like yacc or lex, then we
> can just bundle the generated wrapper files with the release tarball,
> and users won't even need SWIG, let alone SWIG 1.3.25.
>
> I think that this would be a great feature for Subversion 1.3.x. Can
> you explain what changes we'll need to make to our build system? If
> the other Subversion developers are also in support of the change, I
> can do the build system work.
>
> Perhaps it would be a good idea for us to run SWIG when users type
> "autogen.sh"? (The SWIG bindings code would only be generated if SWIG
> 1.3.25 is installed). We already include the generated output of
> "autogen.sh" in the release tarballs.

http://subversion.tigris.org/servlets/ReadMsg?list=dev&msgNo=97162

http://subversion.tigris.org/servlets/ReadMsg?list=dev&msgNo=95920

and the other messages on those threads

and the older rather long thread

http://subversion.tigris.org/servlets/ReadMsg?listName=dev&msgNo=86430

Some of those threads even have patches I wrote... probably don't work
anymore but it is something you can look at.

I don't presume to speek for the developers, but the last time this came
up they seemed to like the idea... but didn't want to do anything prior to
the release.

Just to restate: all the files generated from SWIG 1.3.25 can be included
directly and compiled anywhere... they have absolutly no SWIG
dependencies. If other code needs access to the runtime type system (like
subversion), you just need to run SWIG to generate the header file, and
then that header file is also stand-alone. For more information, you can
read the Modules chapter

http://www.swig.org/Doc1.3/Modules.html

basicly, just run
swig -python -external-runtime <filename>
which I think subversion is already doing... it just isn't doing it before
the build process.

Hope that helps,
John

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Aug 6 21:29:02 2005

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.