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.
Forgive the second reply but on further study of the build log and some googling around, I think the absolute/relative paths are not the culprit, and that your suspicion about calling conventions may be correct.
Which led to:
To summarize, CDECL is default and therefore probably what Subversion is building with, but zlib may be building with STDCALL.
I would check if the zlib project defines ZLIB_WINAPI and if so, remove it and retry the build.
Received on 2018-01-28 07:21:18 CET