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

Re: Python bindings build seems broken

From: Jeremy Whitlock <jcscoobyrs_at_gmail.com>
Date: Mon, 13 Oct 2008 01:42:32 -0600

As of r33610, this has been fixed. r33610 makes SWIG conditionally
include platform-specific auth providers. As I worked on this though,
I found two other problems with SWIG and the auth providers.

1) As the code stands now, you will *never* get keychain or windows
auth providers in the SWIG libraries. While r33610 has code to
conditionally include OSX/Win32 auth providers, it has no impact on
the SWIG libs just yet. The reason this happens is because of the way
their respective auth provider functions are declared. Since each
declaration is within platform-specific "#if defined" blocks, SWIG
cannot see those functions and does not attempt to wrapper them. My
next task is to make SWIG smart enough to get access to the OSX/Win32
auth provider function declarations.

2) Now that SWIG can conditionally wrapper platform-specific auth
providers, when you try to run the bindings, there is a failure at
runtime. The reason for this is that there is no linking done to the
SWIG core library to use the functions in the respective library.
This should not be a problem for OSX/Win32 since their functions are
in libsvn_subr but for gnome-keyring/kwallet, this is an issue. To
fix this, we need to link SWIG core against the gnome-keyring/kwallet
library appropriately. I have mentioned this to Senthil and he is
looking into this.

Take care,


To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-10-13 09:42:44 CEST

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