On 2/17/06, David James <email@example.com> wrote:
> In order to compile Subversion bindings for Python 2.4, you would need
> to use Visual Studio.NET to compile Subversion and its dependencies
> (e.g. APR).
> We normally build Subversion using Visual Studio 6, so we do not build
> Python 2.4 bindings. However, if a volunteer were to build Python 2.4
> bindings using Visual Studio.NET, it would be much appreciated.
> Branko Čibej has mentioned in the past that he feels it is dangerous
> to mix libraries compiled with different versions of Visual Studio on
> the same system. I don't agree. Personally, I often mix DLLs compiled
> with different versions of Visual Studio, and I have never seen any
> If a volunteer were to build Python 2.4 bindings using Visual
> Studio.NET, I would be happy to test them, and check whether there are
> any compatibility problems. I expect that they will work fine.
I agree that from a functional point of view mixing and matching run
time library components with DLL's can work fine provided people are
careful with things like memory management across dll boundaries (e.g.
dont allocate in one and free in the other), because the different run
time libraries have their own heaps.
From a distribution/support point of view, having one set of run time
library dependencies is always easier to manage. ;-)
Thanks for your clarification. Now I understand what you were getting at.
Received on Fri Feb 17 20:52:53 2006