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

Re: 1.3.0 swig issue

From: David James <james82_at_gmail.com>
Date: 2006-01-04 18:02:35 CET

On 1/4/06, Joe Orton <jorton@redhat.com> wrote:
> The 1.3.0 tarball includes sources generated by swig 1.3.25
> (subversion/bindings/swig/perl/native/*.c etc) - this breaks the build
> if using swig 1.3.24, if nothing else. Was that intentional?
> (running "make extraclean-swig-headers" before building seems to work
> around the issue)

What commands are you typing? By default, the 1.3.0 tarball doesn't
use SWIG at all, because the generated SWIG files are shipped with the
tarball. The SWIG bindings should work out of the box, regardless of
whether or not you have SWIG installed. This is a new feature in
Subversion 1.3.0.

Here's how to build the Python bindings for Subversion 1.3.0 from the tarball:
  ./configure && make && make swig-py && make check-swig-py

I'm guessing that you ran autogen.sh without the release flag before
running configure. This switches you to "development mode". Is this
what you want to do?

In development mode, SWIG headers are regenerated automatically as
needed using your installed version of SWIG. To setup a clean
environment for doing development from a tarball, you'll need to run
"make extraclean" first.

Does this 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 Wed Jan 4 18:05:22 2006

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.