[Interest] Compiling Qt from source 64 bit on Windows

Thiago Macieira thiago.macieira at intel.com
Mon Mar 14 21:45:52 CET 2016


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




More information about the Interest mailing list