On Mon, Apr 20, 2020 at 9:59 AM Johan Corveleyn <jcorvel_at_gmail.com> wrote:
> On Sun, Apr 19, 2020 at 11:21 PM Nathan Hartman
> <hartman.nathan_at_gmail.com> wrote:
> > On Sun, Apr 19, 2020 at 1:45 PM Johan Corveleyn <jcorvel_at_gmail.com> wrote:
> > > On Sun, Apr 19, 2020 at 5:47 PM Johan Corveleyn <jcorvel_at_gmail.com> wrote:
> > >> Hi Nathan,
> > >>
> > >> Sure! Any help on the Windows-side of things would be definitely appreciated.
> > Thank you very much for sharing your notes. It doesn't matter that
> > it's a bit rough around the edges; I'll try to take good notes on
> > everything I'm doing as well. I appreciate all your efforts.
> > I haven't needed to boot Windows 10 in some time because my work has
> > shifted to Mac and Linux, so I nuked everything on that machine and
> > I'm starting from a clean slate. I had an image from before installing
> > anything. It's old though, so I've been installing all the service
> > packs. When this part is done, I'll take a more up-to-date "clean"
> > image and then get started. My hope is that by doing it this way, I'll
> > be able to come up with a "complete" sequence of steps that isn't
> > missing anything because of something I happened to have already
> > installed. When I'm finished, this machine will be dedicated to
> > building/testing SVN on Windows.
> One more thing that came to mind: there is another interesting perl
> script in our repository:
> This was originally written by Ben Reser years ago, and probably
> worked pretty well for a while. I think I learned some of the "httpd
> build workarounds" from that script.
> It might be worthwhile to resurrect that script, bring it up to date
> etc. (for instance, I'd drop neon and probably also bdb (or at least
> make it optional), and try to bring all the others up to their latest
> version). Also, it would probably be nice if you could choose between
> "debug" and "release" configuration on the one hand, and "x86" and
> "x64" on the other (two orthogonal axes IIUC). If such a script is
> accompanied by good documentation in INSTALL (and the script itself
> pointing to INSTALL for further info), that would make a good
> combination I think. As in: INSTALL points to the script for easily
> building all dependencies, but at the same time contains all the info
> to do things manually if you want to (and that "manual explanation"
> serves also as explanation of what the script is actually doing).
I started a new thread with all these bits of information about
building on Windows (was getting heavily off-topic from the original
subject of Py3 support :-)):
"Building SVN (dependencies) on Windows"
Please continue further discussion / hints / additions there, thanks.
Received on 2020-04-20 15:38:52 CEST