[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Windows Compile Help

From: Nathan Hartman <hartman.nathan_at_gmail.com>
Date: Sun, 28 Jan 2018 00:33:13 -0500

On Jan 27, 2018, at 11:44 PM, Troy Curtis Jr <troycurtisjr_at_gmail.com> wrote:
>
> I'm hoping someone can point me in the right direction with an issue I'm having compiling Subversion on Windows 10 using Visual Studio 2015 tools.
>
> I decided to break out of my comfort zone a bit and see if I could get the changes in for the py3c dependency added on the Windows side, but I am *not* a Windows dev. I've done a lot of learning, which as been fun, but I can't figure this last error out. I've attached the error log, and my WIP visual studio script that basically got me this far.
>
> It seems to complain the it can't find a handful of symbols related to zlib, but if I look at the static archive I see those names (though there are all those different calling conventions on windows, so maybe that is related to my issue?).
>
> Anyway, I've run out of ideas and was hoping for a little nudge.
> …
>
>
> Troy
> <vs-build.txt>
> <svnbuilderr.txt>

There seems to be a mix of relative and absolute paths with respect to zlib in the build script. I'm writing this on my phone so I can't look at the script while writing this but the ZLIBPROJ variable (if memory serves) is assigned a relative path; the library binaries are copied from there to another relative path location; but the --with-zlib= for building Subversion uses an absolute path starting with C:\ -- perhaps you have a different zlib there? If so then you're building one zlib in this script but using a different zlib when building Subversion, perhaps one built with mingw instead of MSVC or something. That would explain the linker errors. Unless I'm missing something else :-)

Hope this helps
Received on 2018-01-28 06:33:30 CET

This is an archived mail posted to the Subversion Dev mailing list.