[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: David James <james82_at_gmail.com>
Date: 2005-08-05 15:27:09 CEST

> > 3) Drop support for SWIG 1.3.20 and 1.3.21.
> The other solution is what I have been talking about for a while now... as
> of 1.3.25, SWIG is a build time only tool, and the output from SWIG can be
> compiled on any computer. Think lex and yacc... SWIG now functions just
> like them.
> You can read the archives for some discussion on it, but the idea is that
> only the developers would need to have SWIG installed... you could include
> the build output from SWIG directly in the released tarballs. I find this
> idea similar to the reason neon and apr are included in the tarballs.
> If you stick the output .cxx files from SWIG into the svn repository, then
> only when a header or .i file changes will SWIG get invoked. I attempted
> to do this at one point, but the Makefile and python scripts to generate
> Makefiles were confusing so I didn't go that deep into it.
> The other advantage is that the developers can stay current with SWIG
> releases, geting all the bug fixes and such...
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.

> > 1) Find some way to make Subversion and SWIG 1.3.20 and SWIG 1.3.21's
> > runtime lookup system work well together.
> The biggest problem with this is that before 1.3.23 or so, the runtime
> type stuff was a huge mess. It was using tons of hacks, the code was very
> difficult to follow, etc. With 1.3.25 for sure, the run time type stuff,
> while it didn't change much in functionality, got a lot easier to
> understand and the code is much more straight forward.

This isn't a problem if we run SWIG in "autogen.sh", and bundle the
generated "C" files in the tarball.

Thanks for your help!


David James -- http://www.cs.toronto.edu/~james
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Aug 5 15:28:03 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.