On Tue, Apr 21, 2020 at 9:33 PM Barry Scott <ba...@barrys-emacs.org> wrote: > > I know this pain well. I build svn for macOS and Windows to do the binary > pysvn releases. > > I have the build for the svn client side of things fully automated. > In case this is helpful to you here is what I use. > > The scripts I use are here: > > https://svn.code.sf.net/p/pysvn/code/trunk/pysvn/ReleaseEngineering/Windows > > The build-all-deps.cmd is the entry point thats get you to a working svn > client. > > To build svn 1.13 compatible with python 3.5 and later I use: > > build-all-deps 3.5 1.13 win64 > > The version of the source code to use is setup in build-config-svn-1.13.cmd. > > Any patches that are needed to make the builds work are in: > > https://svn.code.sf.net/p/pysvn/code/trunk/pysvn/ReleaseEngineering/Windows/patches > > And you would need to have the compilers installed and the source kits of all > the > deps for the above to work of course. > > Barry
Hi Barry, Thanks a lot for sharing. Yes, it can be so hard :-). I do need to build all of it myself (not only the client), for testing and signing off on the release, so including mod_dav_svn etc. But scripts that can build the client easily might already be a big help to some. And the build patches can certainly be useful. I'll try to take a closer look later (or perhaps someone else here will), but thanks already for sending your bits and pieces here :-). -- Johan