RE: Building SVN (dependencies) on Windows
Date: Wed, 6 May 2020 12:32:40 +0200
Quite a few of the Windows dependencies can easily be built by the VCPKG package manager.
For SharpSvn I maintained quite a few custom NAnt scripts that do about the same work (https://ctf.open.collab.net/svn/repos/sharpsvn/trunk/imports
(or <https://github.com/AmpScm/SharpSvn/tree/master/imports> https://github.com/AmpScm/SharpSvn/tree/master/imports, but I think this mirror lags a bit )
Somewhere in the CollabNet open source repositories there should be a slightly simpler -not as many development options- MSBuild version of the scripts to build the dependencies, but I’m not sure at which url.
Van: Graham Bloice <graham.bloice_at_trihedral.com>
Apologies for butting in, but as a long time maintainer of the (mainly Windows) build process for Wireshark, another cross platform project, I'd like to offer my thoughts on such matters to the svn project.
1. We moved to CMake quite some time ago, getting rid of automake and nmake and VS solution files. Such a relief to have one build tool, usable on all platforms. This is obviously a big step to take.
I see a number of advantages with the Wireshark solution:
1. Much smaller barrier to entry for those attempting to build. Still quite a setup needed, hence the developer's guide step-by-step section, see here:https://www.wireshark.org/docs/wsdg_html_chunked/ChSetupWin32.html
You can see the sausages being made over at the Wireshark buildbot: https://buildbot.wireshark.org/wireshark-master/waterfall, in particular the "ran CMake" generation step, although if there are no updates to the libraries it's a standard CMake experience.
I'm not subscribed to the list, just observe infrequently via the svn.haxx.se <http://svn.haxx.se> archive, so if you have any questions please add me in replies.
P.S. I did build svn on Windows once, many years ago and I found it an awkward process.
-- Graham BloiceReceived on 2020-05-06 12:32:47 CEST
This is an archived mail posted to the Subversion Dev mailing list.