[Interest] Compiling Qt from source 64 bit on Windows

[Nuno Santos]

Kai,

To whom should I pass the -static-runtime option? To Qt configure or to Openssl libs? 

When I compile Qt from source I modify msvc-desktop.conf to use MT instead of MD which comes by default.

The Openssl libs are pre compiled and they provide binaries for both 32 and 64 bit.

With a 32 bit build of Qt everything is alright. 

Regards,

Nuno

> On 15 Mar 2016, at 07:52, Koehne Kai <Kai.Koehne at theqtcompany.com> wrote:
> 
> 
> 
>> -----Original Message-----
>> From: Interest [mailto:interest-
>> bounces+kai.koehne=theqtcompany.com at qt-project.org] On Behalf Of
>> Nuno Santos
>> Sent: Monday, March 14, 2016 7:12 PM
>> To: interest at qt-project.org
>> Subject: [Interest] Compiling Qt from source 64 bit on Windows
>> 
>> Hi,
>> 
>> Is there any special difference in compiling Qt from source in Windows in 64
>> bit?
>> 
>> This is my configure linke
>> configure -prefix c:\qt\5.6\msvc2013_opengl_5_6_rc_64_static -
>> commercial -debug-and-release -static -nomake examples -nomake tools -
>> nomake tests -opengl dynamic -skip multimedia -openssl-linked -I
>> c:\openssl-lib\include -L c:\openssl-lib\lib64
>> OPENSSL_LIBS_DEBUG="ssleay32MTd.lib libeay32MTd.lib"
>> OPENSSL_LIBS_RELEASE="ssleay32MT.lib libeay32MT.lib"
> 
> You're linking against the MT version of openssl libs, but do not pass '-static-runtime' as configure argument - so the Qt libs will link against the MD versions of the runtime libs. I wouldn't be surprised if this causes linking issues like yours.
> 
> Regards
> 
> Kai 
>