I am the build-master for the Exiv2 project. http://exiv2.org
<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 because I believe the
compiler generates run-time and other library references that may cause issues.
To make life even more difficult, I encourage you to avoid CMake/Visual Studio
as they dance with the elegance of two sumo wrestlers.
I provide build support for Exiv2 on several popular build systems. Our
current MSVC build environment builds libssh (0.55) with openssl (1.0.1j). We
also provide build support for CMake/Visual Studio.
2012-05-04 23:35 <DIR> expat <--- "vanilla" expat 2.1.0
source tree
2012-05-04 23:35 <DIR> zlib <--- "vanilla" zlib 1.2.7
source tree
2012-05-04 23:35 <DIR> curl <--- "vanilla" curl 7.39.0
source tree
2012-05-04 23:35 <DIR> openssl <--- "vanilla" openssl 1.0.1j
source tree
2012-05-04 23:35 <DIR> libssh <--- "vanilla" libssh 0.5.5
source tree
You may find our build code helps you to build libssh with MSVC. Our build
environments support VS 2005/8/10/12/13/15 and 2017/RC. We also support GCC
(and/or clang) on MinGW, Cygwin, Linux and MacOS-X.
Robin
http://clanmills.com
> On 24 Nov 2016, at 14:35, Aris Adamantiadis <[email protected]> wrote:
>
> 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 compilers for C is not a problem,
> but it's windows here :)
>
> Aris
>
> On 23/11/16 18:13, 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 openssl
>> 1.0.1. I could I guess try openssl 0.9 but that is now unsupported.
>>
>> Mark
>>
>> On 23/11/2016, 17:10, "Aris Adamantiadis" <[email protected]> wrote:
>>
>> Hi Mark,
>>
>> The first error is caused because VS2008 does not fully support c99. I
>> think simply removing the broken include should work, we have
>> alternatives to stdint.h at least in other include files.
>> Which libssh version are you using? I couldn't map the line numbers to
>> v0-7 or master. I think that the problem is caused by c99-style
>> structure initializations. There are other places in libssh that use
>> them and I'm not sure this can be easily fixed without losing the
>> advantage of this 15 years-old C feature.
>>
>> Aris
>>
>>
>> On 23/11/16 17:59, Mark Ramsden wrote:
>>>
>>> Hi.
>>>
>>>
>>>
>>> I am really stuck trying to build libssh on MSVC Visual Studio 9. I
>>> have installed and built open ssl 1.0.1 and run cmake on lib ssh and
>>> get a make file but now I have 2 problems.
>>>
>>>
>>>
>>> I get this error
>>>
>>>
>>>
>>> \src\external\blowfish.c(52) : fatal error C1083: Cannot open include
>>> file: 'stdint.h': No such file or directory
>>>
>>>
>>>
>>>
>>>
>>> and also libcrypto will not compile
>>>
>>>
>>>
>>> 2>..\..\src\libcrypto.c(705) : error C2059: syntax error : '.'
>>>
>>> 2>..\..\src\libcrypto.c(731) : error C2059: syntax error : ','
>>>
>>> 2>..\..\src\libcrypto.c(742) : error C2059: syntax error : ','
>>>
>>> 2>..\..\src\libcrypto.c(753) : error C2059: syntax error : ','
>>>
>>> 2>..\..\src\libcrypto.c(800) : error C2059: syntax error : ','
>>>
>>> 2>..\..\src\libcrypto.c(811) : error C2059: syntax error : ','
>>>
>>> 2>..\..\src\libcrypto.c(822) : error C2059: syntax error : ','
>>>
>>> 2>..\..\src\libcrypto.c(835) : error C2059: syntax error : ','
>>>
>>> 2>..\..\src\libcrypto.c(846) : error C2059: syntax error : ','
>>>
>>> 2>..\..\src\libcrypto.c(857) : error C2059: syntax error : ','
>>>
>>> 2>..\..\src\libcrypto.c(862) : error C2059: syntax error : '}'
>>>
>>>
>>>
>>> I’, guessing this is because the Microsoft compiler is not allowing
>>> the C like code.
>>>
>>>
>>>
>>> Has anybody come up against this or any ideas how I could fix this ?
>>>
>>>
>>>
>>> Any help would be gratefully received
>>>
>>>
>>>
>>> ESP Leisure
>>> website <http://www.e-s-p.com/> facebook
>>> <http://www.facebook.com/ESPLeisure> twitter
>>> <http://twitter.com/ESPLeisure> LinkedIN
>>> <http://www.linkedin.com/company/2284332>
>>> Mark Ramsden
>>> Systems Analyst
>>> ESP Leisure Ltd
>>>
>>> Europa House, Kimpton Link Business Park, Kimpton Road, Sutton, Surrey
>>> SM3 9QP
>>> +44 (0)20 8251 5100
>>> /
>>> Winner of the Center Parcs Service and Product Innovation Award 2014/
>>> This message may contain information that is not intended for you. If
>>> you are not the addressee or if this message was sent to you in error,
>>> you are requested to inform the sender and delete the message. ESP
>>> Leisure, Registered in England (reg no 2550976) Registered office:
>>> Europa House, Kimpton Link Business Park, Kimpton Road, Sutton, Surrey
>>> SM3 9QP
>>>
>>
>>
>>
>>
>>
>> [ESP Leisure]
>> [website]<http://www.e-s-p.com/> [facebook]
>> <http://www.facebook.com/ESPLeisure> [twitter]
>> <http://twitter.com/ESPLeisure> [LinkedIN]
>> <http://www.linkedin.com/company/2284332>
>> Mark Ramsden
>> Systems Analyst
>>
>> ESP Leisure Ltd
>>
>> Europa House, Kimpton Link Business Park, Kimpton Road, Sutton, Surrey SM3
>> 9QP
>> +44 (0)20 8251 5100
>>
>> [http://www.e-s-p.com/email_images/centerparcs_tiny.png]
>> Winner of the Center Parcs Service and Product Innovation Award 2014
>> This message may contain information that is not intended for you. If you
>> are not the addressee or if this message was sent to you in error, you are
>> requested to inform the sender and delete the message. ESP Leisure,
>> Registered in England (reg no 2550976) Registered office: Europa House,
>> Kimpton Link Business Park, Kimpton Road, Sutton, Surrey SM3 9QP
>>
>
>
