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

RE: Building my own Python bindings; is there a test for it?

From: Dale Hirt <dale_at_sbcltd.com>
Date: 2005-09-28 00:26:01 CEST


You should be fine as long as it's the same source tree you used for the initial installation.

The bindings are separate from the initial install, but they do use the libs you already created. They don't munge them in any way.


-----Original Message-----
From: Matt England [mailto:mengland@mengland.net]
Sent: Tuesday, September 27, 2005 3:21 PM
To: Matthew England
Cc: Dale Hirt; SVN Users email list
Subject: Re: Building my own Python bindings; is there a test for it?

At 9/27/2005 08:23 AM, Matt England wrote:
>>>8) make swig-py
>>>9) make install-swig-py
>Uhh, nevermind. I couldn't get the make off the ground [...]

Well, that was because I didn't have SWIG installed (didn't know I needed
that). So I built and installed SWIG, then I can now run 'make swig-py' in
my Subversion build source extract directory.

My question before I run 'make install-swig-py': can I do all this swig-py
installation *after* I've already installed the SVN "core" _minus_ the
SWIG/Pythong stuff? Do I need to change any of existing, installed SVN

I'm presuming not, and am proceeding with running 'make install-swig-py'
after the fact...but I would like someone to confirm that this is ok or
tell me what I need to do otherwise (and if I need to rebuild all of
Subversion again with the new SWIG dependencies, etc).


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Sep 28 00:27:44 2005

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.