subversion-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bert Huijben" <b...@qqmail.nl>
Subject RE: building SVN trunk on Windows fails on python gen-make.py
Date Mon, 22 Jun 2015 12:31:48 GMT
> -----Original Message-----
> From: Cooke, Mark [mailto:mark.cooke@siemens.com]
> Sent: maandag 22 juni 2015 13:46
> To: Stefan Hett; users@subversion.apache.org
> Subject: RE: building SVN trunk on Windows fails on python gen-make.py
> 
> Sorry I cannot help with the current issue but I wanted to add a comment about
> the content of INSTALL (below)...


> While I agree in principle, I need to build httpd and subversion to work with
> Trac (trac.edgewall.org) which is currently limited to python < 3.0 (I use 2.7
> also).  For this to work properly my understanding is that httpd and python (and
> svn) all need to use the same compiler libraries and Python 2.7 is built using
> Visual C++ 2008...
> 
> So the 2008 stuff is not completely irrelevant (I got it compiling and making the
> python bindings).  I have some notes but they are not really fit for publication
> and are for VC2008 but I can share them if you think they would be useful.

To build AnkhSVN for Visual Studio 2005 and 2008 I continue to build Subversion using VS 2008
at least every week, so I would consider VS 2005 and 2008 as fully supported for Subversion.

But I don't think anybody working on Subversion really uses VS 6.0 (released +- 18 years ago)
or 2002 and 2003, so I don't consider our support for these versions as really supported.
I'm guessing that the VS 6.0 support might still work with a minor tweak, while I think the
2002/2003 support would need at least some patches to make it work again.

If nobody is going to comment on this after the release of 1.9.0, I think we will drop support
for these 12+ year old versions with 1.10+.  With VS 2013 Community Edition now free to use
for everybody working on open source projects, there is no good reason to continue to support
these very old versions, that target platforms that are no longer supported anyway.


One interesting point for some usecases is that the VS 2010 tooling allows building with the
VS2008 compiler by passing a few specific flags to msbuild. This is how the first version
of XP compatibility in VS2012+ was implemented. (And this is also how VC 2010+'s C++/CLI can
target .Net 2.0-3.5)

	Bert



Mime
View raw message