Comments on: Compiling Subversion Python bindings on Windows

By: Lars Erik Jordet

Lars Erik Jordet — Tue, 15 Feb 2011 12:27:02 +0000

Haha, “oops”; Fixed now.

Though I’m not sure if 2008 is available for download anymore – I have to check if this actually works with 2010.

By: Yoyosan

Yoyosan — Sat, 12 Feb 2011 16:58:27 +0000

Could you correct the requirements paragraph to say Visual C++ instead of C#.
Thanks

By: windows下编译subversion的Python绑定（附下载） - 木哈哈

windows下编译subversion的Python绑定（附下载） - 木哈哈 — Sun, 16 Jan 2011 12:07:42 +0000

[...] 由于svn的python绑定一直没有推出python2.7的版本，所以只好自己编译了。参考链接：http://www.lejordet.com/2009/03/compiling-subversion-python-bindings-on-windows/ [...]

By: Dawuid

Dawuid — Wed, 05 Jan 2011 14:28:03 +0000

If _USE_32BIT_TIME_T preprocessor definition is added to APR and SWG_PYTHON projects, builded dlls works fine. The package obtained is similar to package available in http://alagazam.net/ (only *.py, _*.dll and libsvn_swig_py-1.dll are need to be copied to libsvn). Such package works fine with Trac and Subversion deployed in Apache 2.2.

Not using _USE_32BIT_TIME_T preprocessor definition change libapr _apr_time_ansi_put@8 to _apr_time_ansi_put@12 (time_t is compiled like 64bits instead 32bits). And that brings problems with Apache and subversion libraries.

By: Synesthesia

Synesthesia — Tue, 03 Aug 2010 21:03:08 +0000

[...] Compiling Subversion Python bindings on Windows [...]

By: Allard

Allard — Thu, 01 Apr 2010 20:12:35 +0000

This action:
Do a Windows search for “*.dll” in C:\Temp\subversion-1.6.9\Release\subversion

should be replaced by:
Do a Windows search for “*.dll” in C:\Temp\subversion-1.6.9

else you mis the APR dll’s and will get the python error:
ImportError: DLL load failed: The specified module could not be found.

By: lejordet

lejordet — Wed, 02 Sep 2009 06:16:24 +0000

I’ve been trying to repeat this for building SVN 1.6.5, and I’ve had some strange problems that didn’t occur the first time around – I’ll investigate if it’s due to changing the SVN version, or if there’s a problem with the procedure.

Notable changes:
- apr_* will build, but have 8-9 failed builds – the database modules won’t build unless you add in the proper libraries, which is outside the scope of this article, for now.
- You might have to force VS2008 to recognize where your python.exe is found (Adding the path manually in options), otherwise some parts of the base library will build successfully (or so it seems), except there’s a line about not finding “python”, and nothing is really built.

After a bit of work I got it to build, but the finished product, the .pyd/.py files, don’t work…

By: lejordet

lejordet — Mon, 31 Aug 2009 18:29:12 +0000

Are you building all or just “__SWIG_PYTHON__”? I’ll try this again to update a newer version, so I’ll revise the steps if they’ve become incorrect in the mean time.

By: Chris

Chris — Mon, 31 Aug 2009 18:24:54 +0000

Interesting article, but I can’t get past the Visual Studio step.

aprutil.dsw fails with 6 errors like:
7>.\apr_dbd_mysql.c(29) : fatal error C1083: Cannot open include file: ‘mysql.h’: No such file or directory
8>.\apr_dbd_freetds.c(39) : fatal error C1083: Cannot open include file: ‘sybdb.h’: No such file or directory

subversion_vcnet.sln compiles without errors, but doesn’t create any files in C:\Temp\subversion-1.6.0\subversion\bindings\swig\python\. Only folders with names like python_repos, python_fs, etc.

By: Making a Trac install work on Apache 2.2/Python 2.6/win32 - Saved for later reference

Mon, 30 Mar 2009 11:52:52 +0000

[...] Follow my previous guide to compile and install Python SVN bindings. [...]