Thiago, Thanks for the clarification. I will investigate further.
Thanks, Regards, Nuno > On 14 Mar 2016, at 20:45, Thiago Macieira <thiago.macie...@intel.com> wrote: > > 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@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@QEAA@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@qt-project.org > http://lists.qt-project.org/mailman/listinfo/interest _______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
