You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Matt England <me...@mengland.net> on 2005/09/27 13:17:15 UTC

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

Since I'm rebuilding subversion 1.2.3, I decided to make my own python 
bindings from source to run Dale Hirt's RepoMerge.py script:

>8) make swig-py
>9) make install-swig-py

...as part of the procedure noted below.  Is this procedure order is 
correct?  Is there a test for these bindings like the 'make check' overall 
test?

-Matt


>Date: Tue, 27 Sep 2005 06:21:22 -0500
>To: bob@proulx.com (Bob Proulx)
>From: Matt England <me...@mengland.net>
>Subject: Re: Minimal build instructions for svnserver & fsfs only?
>Cc: users@subversion.tigris.org,Matt England <me...@mengland.net>
>
>At 9/26/2005 10:50 PM, Bob Proulx wrote:
>>Because you say you are running on a GNU/Linux and would normally use 
>>shared libraries there I would use the following configure options:
>>
>>   ./configure --without-berkeley-db
>>
>>Then check the resulting shared libraries that are linked against the
>>svn binary.
>>
>>   ldd svn
>
>Ahh, this seems to make sense.  Very helpful.
>
>Additionally note:  I found (via ldd) I had a ton of dependencies on 
>external, old svn/apr/etc libs...and hence I probably need (or at least I 
>presume) to update the procedure to delete said libs in advance prior to 
>running the build.  Updated procedure follows.
>
>Also: I want to run Dale Hirt's (sp?) python script to merge repositories, 
>hence I want to install the python bindings.  Should I run the 'make 
>swig-py' and 'make install-swig-py' commands at the end of the procedure 
>as per below?
>
>1) delete the following from <prefix>/lib: libsvn*, libapr*, libneon*
>2) extract the tarball for subversion-x.y.z
>3) cd into subversion-x.y.z
>4) ./configure --without-berkeley-db --prefix=<prefix>
>5) make
>6) make check
>7) make install
>8) make swig-py
>9) make install-swig-py
>
>Unfortunately, this brings down the existing server for the duration of 
>the build.  No fun, but hence I'm up early in the morning so as to not 
>break stuff for my developers.
>
>Is my analysis and procedure correct?
>
>-Matt


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

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

Posted by Matt England <me...@mengland.net>.
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 
binaries/libs/targets?

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).

Thanks,
-Matt 


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

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

Posted by Matt England <me...@mengland.net>.
At 9/27/2005 08:17 AM, Matt England wrote:
>Since I'm rebuilding subversion 1.2.3, I decided to make my own python 
>bindings from source to run Dale Hirt's RepoMerge.py script:
>
>>8) make swig-py
>>9) make install-swig-py

Uhh, nevermind.  I couldn't get the make off the ground, and I'm not up to 
debugging makefiles at the moment.  Details below.

Dale earlier sent me references to precompiled python bindings earlier, 
I'll go use those.

A side question: what exactly are "bindings" or "python bindings"?  I'm 
assume they are links/bridges to use Subversion commands/mechanisms in the 
Python language (or any other language in a binding) rather then having to 
call external "svn" cmdline calls using something like system(3)...but I 
thought I'd check to make sure.

-Matt

mengland@myhost 8:19am [...builds/subversion-1.2.3] 87> date
Tue Sep 27 08:19:41 CDT 2005
mengland@myhost 8:19am [...builds/subversion-1.2.3] 88> uname -a
Linux myhost.com 2.4.20-021stab028.17.777-enterprise #1 SMP Tue Jul 19 
19:31:27 MSD 2005 i686 i686 i386 GNU/Linux
mengland@myhost 8:19am [...builds/subversion-1.2.3] 89> make swig-py
none  -python -I/home/builds/subversion-1.2.3/subversion/bindings/swig 
-I/home/builds/subversion-1.2.3/subversion/include -I -DSVN_SWIG_VERSION= 
-DSWIG_TABLE_TYPE=subversion 
-I/home/builds/subversion-1.2.3/apr/include 
-I/home/builds/subversion-1.2.3/apr-util/include 
-I/home/builds/subversion-1.2.3/subversion/bindings/swig/python/libsvn_swig_py 
-o subversion/bindings/swig/python/svn_client.c 
/home/builds/subversion-1.2.3/subversion/bindings/swig/svn_client.i
make: none: Command not found
make: *** [subversion/bindings/swig/python/svn_client.c] Error 127
mengland@myhost 8:19am [...builds/subversion-1.2.3] 90>



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org