[Interest] Compiling Qt from source 64 bit on Windows

[Gunnar Roth]

Hi Thiago, you probably missed the -static configure option, so Nunos is making a static qt build. He really should mention that in the subject line.
Ordinary 64 bit windows qt 5.6rc builds worked for me without a problem with vs2012 an 2015.

libcpmt.lib is the c++ multithread static lib of visual studio. 


 
Regards,
Gunnar Roth


> Am 14.03.2016 um 21:45 schrieb Thiago Macieira <thiago.macieira at intel.com>:
> 
> On segunda-feira, 14 de março de 2016 18:11:46 PDT Nuno Santos wrote:
>> Hi,
>> 
>> Is there any special difference in compiling Qt from source in Windows
>> in 64 bit?
> 
> No. It's been working just fine for the last 3 or 4 years for me.
> 
>> libcpmt.lib(locale.obj) : error LNK2001: unresolved external symbol
>> _purecall
> 
>> libcpmt.lib(xthrow.obj) : error LNK2019: unresolved external symbol
>> _purecall referenced in function "public: __cdecl
>> std::basic_string<char,struct std::char_traits<char>,class
>> std::allocator<char> >::basic_string<char,struct
>> std::char_traits<char>,class std::allocator<char> >(char const *)"
>> (??0?$basic_string at DU?$char_traits at D@std@@V?$allocator at D@2@@std@@QEAA at PEBD@Z
>> )
> 
> Looks like your environment wasn't set up properly. This library (libcpmt.lib) 
> is requiring functions that aren't present.
> 
> I've never heard of libcpmt, so I have no idea what it's supposed to be doing 
> or how you got linking to it. My guess is that the OpenSSL libraries are 
> causing it, somehow. I suggest you go back to dynamic loading of the OpenSSL 
> libraries, instead of -openssl-linked.
> 
> -- 
> Thiago Macieira - thiago.macieira (AT) intel.com
>  Software Architect - Intel Open Source Technology Center
> 
> _______________________________________________
> Interest mailing list
> Interest at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest