Re: SWIG and platform-specific auth providers (Was: Python bindings build seems broken)

> Slick idea. After r33671 and r33707 I'm still having a bit of trouble with the
> Ruby bindings. I think the issue is that SWIGWIN is defined empty when the
> PLATFORM_SPECIFIC_WRAPPER macro is expanded by SWIG, so I ended up with a
> #ifdef with no macro to test the definition of when trying to actually compile
> the bindings.
>
> Attached is a patch that uses a new macro SVN_SWIG_WINDOWS that is not defined
> when PLATFORM_SPECIFIC_WRAPPER is expanded, and then is defined later. Does
> this sound reasonable? Is there a better name for the new macro? Is there a
> better place for it to be defined?

Thanks for the patch but I think it's a moot point. I'm currently
refactoring the auth providers and it should be ready for commit
tomorrow. For more details about the refactoring, please review the
following thread:

http://www.nabble.com/Configuring-encrypted-password-caching:-API-proposal-td20017581.html

-- 
Take care,
Jeremy Whitlock
http://www.thoughtspark.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org