You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Joe Orton <jo...@redhat.com> on 2006/01/04 13:55:30 UTC
1.3.0 swig issue
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)
Regards,
joe
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: 1.3.0 swig issue
Posted by Joe Orton <jo...@redhat.com>.
On Wed, Jan 04, 2006 at 12:02:35PM -0500, David James wrote:
> 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?
Sorry, my mistake, that was indeed the problem. Thanks.
joe
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: 1.3.0 swig issue
Posted by David James <ja...@gmail.com>.
On 1/4/06, Joe Orton <jo...@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?
Cheers,
David
--
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
Re: 1.3.0 swig issue
Posted by Ben Collins-Sussman <su...@red-bean.com>.
On 1/4/06, Joe Orton <jo...@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?
>
What do you mean by 'breaks the build'? Is our ./configure still
erroneously searching for run-time swig libraries, even though the .c
code has already been generated by the tarball packager?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org