Re: Microsoft visual C++ compilation problems

Mark, I provided a patch for this Windows link issue earlier, but it has not been accepted yet. Here it is again for you: src/session.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/src/session.c b/src/session.c index c29af1e..f6d926a 100644 --- a/src/session.c +++ b/src/session.c @

Re: Microsoft visual C++ compilation problems

Robin, Thanks for this I will take a look a bit latter. I have to agree with you about Cmake seems to be the tool of the devil From: Robin Mills on behalf of Robin Mills Reply-To: "libssh@libssh.org" Date: Thursday, 24 November 2016 at 09:53 To: "libssh@libssh.org" Subject: Re: Microsoft vi

Re: Microsoft visual C++ compilation problems

Made a mistake with the openssl was v 1.10 not 1.0.1 so grabbed a copy of that from git and still cannot get it to compile with VS 2009 with the v0-7 build getting a link error error LNK2019: unresolved external symbol _ssh_agent_state_free referenced in function _ssh_free I like to think I’m

Re: Microsoft visual C++ compilation problems

On Wednesday, 23 November 2016 17:13:39 CET Mark Ramsden wrote: > Aris, > > Thanks for quick response. The first as you say should be easily fixable. > > The second I have pulled from Master and yeah it seems to be the C99 thing. > I would use V0-7 branch but this simply does not play nice with o

Re: Microsoft visual C++ compilation problems

I am the build-master for the Exiv2 project. http://exiv2.org I never mix GCC and Microsoft Compiled Code. I believe name mangling is not part of the C++ language and so the code cannot be linked. Additionally, I never mix code compiled with different versions of MSVC beca

Re: Microsoft visual C++ compilation problems

It's strange, do you know what's causing problems with openssl ? v0-7 should work with openssl 1.0.1. It's openssl 1.1 that requires important changes. About the other compiler question: I'm not qualified enough with windows to tell if that should work or not. On sane operating systems, mixing comp