Hi Bert,
do you want me to attempt to update the INSTALL document and remove
references to VC6/VS.NET (2002/2003) and provide a new patch with the
changes against trunk?
Regards,
Stefan
-----Original Message-----
From: Stefan Hett [mailto:ste...@egosoft.com]
Sent: woensdag 22 april 2015 16:35
To: dev@subversion.apache.org
Subject: [PATCH] small INSTALL file corrections
Hi,
following the INSTALL documentation I took the chance to correct a few
minor things I spotted.
Here's a patch containing the changes, in case you want to apply it to
the source (patch against trunk):
[[[
Several small updates/corrections to the INSTALL file:
- mention VS 2010 compatibility
- case-correction for February
- replaced dead-link to Platform SDK for VC6 with link to still
available instructions
- replaced redirection URL zlib.org with direct URL zlib.net
- update VS build instructions to be suitable for VS >= 2010
- added missing compatibility note for VS 2008
* INSTALL
documentation updated
]]]
^> Index: INSTALL
^> ===================================================================
^> --- INSTALL (revision 1675365)
^> +++ INSTALL (working copy)
^> @@ -751,13 +751,13 @@ II. INSTALLATION
^> E.1 Prerequisites
^>
^> * Visual Studio 6 and service pack. It can be built with later
versions
^> - of Visual Studio (Visual Studio.NET 2002, 2003, 2005, 2008 and
Visual
^> + of Visual Studio (Visual Studio.NET 2002, 2003, 2005, 2008, 2010
and Visual
I doubt if Visual Studio 2002 and 2003 still work. I don't think so.
Visual Studio 2012, 2013 and the current prerelease of 2015 are supported.
^> C++ Express 2005, 2008) but these instructions assume VS6.
^> * A recent Windows SDK. (Not needed with Visual Studio 2005 and later)
^> If you are using Visual Studio 6, you need the latest SDK which
^> - is compatible with VC6, which is the one from february 2003.
^> + is compatible with VC6, which is the one from February 2003.
^> You can get it from MSDN:
^> -
http://www.microsoft.com/msdownload/platformsdk/sdkupdate/psdk-full.htm
^> +
https://social.msdn.microsoft.com/Forums/windowsdesktop/en-US/e1147034-9b0b-4494-a5bc-6dfebb6b7eb1/download-and-install-microsoft-platform-sdk-febuary-2003-last-version-with-vc6-support?forum=windowssdk
^> * Python 2.5 or higher, downloaded from http://www.python.org/ which
is
^> used to generate the project files.
^> * Perl 5.8 or higher from http://www.activestate.com/
^> @@ -771,7 +771,7 @@ II. INSTALLATION
^> checkout and have not downloaded Apache 2, then get these 3
libraries
^> from http://www.apache.org/dist/apr/.
^> * ZLib 1.2 or higher is required and is included in the Subversion
^> - dependencies zip file or can be obtained from http://www.zlib.org
^> + dependencies zip file or can be obtained from http://www.zlib.net/
^> * Either a Subversion client binary from
http://subversion.apache.org/ to
^> do the initial checkout of the Subversion source or the zip file
^> source distribution. See the section "Bootstrapping from a Zip or
^> @@ -981,7 +981,7 @@ II. INSTALLATION
^> followed the 'Register the SDK with Visual Studio 6' instructions
^> above this has been done for you).
^> * If you are using Visual Studio .NET change -t dsw into -t vcproj and
^> - add the --vsnet-version=200x option on the gen-make.py command.
^> + add the --vsnet-version=20xx option on the gen-make.py command.
^> In this case you will also have to distribute the C runtime dll with
^> the binaries. Also, since Apache/APR do not provide .vcproj files,
^> you will need to convert the Apache/APR .dsp files to .vcproj files
^> @@ -1012,7 +1012,7 @@ II. INSTALLATION
^> C:>msdev subversion_msvc.dsw /USEENV /MAKE "__ALL_TESTS__ - Win32
Release"
^> C:>cd ..
^>
^> - Or, with Visual C++.NET 2002, 2003, 2005:
^> + Or, with Visual C++.NET 2002, 2003, 2005, 2008, 2010:
^>
^> C:>devenv subversion_vcnet.sln /build "Release" /project
"__ALL_TESTS__"
^> C:>cd ..
I would recommend msbuild /t:__ALL_TESTS__ with modern versions of Visual
Studio, as that avoids doing a lot of unneeded IO. The other option is opening
the solution in Visual Studio and building from there, but running devenv for a
commandline build doesn't give you access to errors and warnings.
Bert
