[Interest] Compile issues Qt5.5.0 with msvc2010 and openssl

[md at rpzdesign.com]

Mathieu:

If you feel that the openssl stuff is a pain to work with,
you can always to link https://tls.mbed.org/ into your projects.

(I am sure WolfSSL would work too)

I decided against OpenSSL when they keep announcing security holes by 
wayward contributors.

It is now code owned and open sourced by ARM and I find it very usable
and manageable to include with qt project code.

The ultimate overhead for its inclusion is 250k on OSX and 500k on Android.

One possible downside is that you are not working with 
NetworkAccessManager at that point, which may or may not be important
to you.

Just an alternate idea.

md

That way you can separate

On 8/21/2015 8:31 AM, Mathieu Slabbinck wrote:
> Koehne Kai was on the right end here :)
> Everything I had was MT, but I had to compile openssl myself against
> msvc2010 to get it to work.
> Thanks!
>
> On Fri, Aug 21, 2015 at 8:01 AM, Koehne Kai <Kai.Koehne at theqtcompany.com> wrote:
>>
>>
>>> -----Original Message-----
>>> From: interest-bounces+kai.koehne=theqtcompany.com at qt-project.org
>>> [mailto:interest-bounces+kai.koehne=theqtcompany.com at qt-project.org]
>>> On Behalf Of Thiago Macieira
>>> Sent: Thursday, August 20, 2015 6:17 PM
>>> To: interest at qt-project.org
>>> Subject: Re: [Interest] Compile issues Qt5.5.0 with msvc2010 and openssl
>>>
>>> On Thursday 20 August 2015 11:20:26 Mathieu Slabbinck wrote:
>>>> -lGdi32" OPENSSL_LIBS_DEBUG="-lssleay32MTd -llibeay32MTd"
>>>> OPENSSL_LIBS_RELEASE="-lssleay32MT -llibeay32MT"
>>>
>>>> cl -c -FIQtXmlPatternsDepends -YuQtXmlPatternsDepends
>>>> -Fp.pch\release\Qt5XmlPatterns_pch.pch -nologo -Zc:wchar_t -arch:SSE2
>>>> -O2 -MD -EHsc -GR -W3 -w34100 -w34189 -w44996 -DUNICODE -DWIN32
>>>
>>> You're building code with -MD and linking an MT library. You cannot do
>>> that.
>>>
>>> Choose one only: -MT or -MD.
>>
>> The actual missing symbol " ___report_rangecheckfailure" though hints that your openssl static libs have been compiled with Visual Studio 2012 or newer, while you try to link now with Visual Studio 2010. I'm pretty sure this isn't supported by Visual Studio, even though openssl is C only.
>>
>> Regards
>>
>> Kai
>> _______________________________________________
>> Interest mailing list
>> Interest at qt-project.org
>> http://lists.qt-project.org/mailman/listinfo/interest
> _______________________________________________
> Interest mailing list
> Interest at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest
>

-- 
No spell checkers were harmed during the creation of this message.