[Interest] Can't build Qt 5.10 statically from source on Windows - fails to link with OpenSSL

[Nuno Santos]

Thiago,

I have tried to set 

set OPENSSL_LIBS=-L c:\openssl-lib-1.1\lib libsslMTd.lib libcryptoMTd.lib

instead of

set OPENSSL_LIBS='-L c:\openssl-lib-1.1\lib libsslMTd.lib libcryptoMTd.lib’

Then I clean the build dir, configured again and build. This time the lib path is not being set at all.

So, if I use the first command, it does add the /LIBPATH: command to the makefile but with extra quotes, that ruin everything

If I use the second command it does not add the /LIBPATH: command to the makefile at all.

In 5.8 configured used to tell us that we should use OPENSSL_LIBS_DEBUG and OPENSSL_LIBS_RELEASE vars. Now there is only OPENSSL_LIBS. Something has definitely changed. I’m unable to built it.

Regards,

Nuno

> On 27 Oct 2017, at 16:38, Nuno Santos <nunosantos at imaginando.pt> wrote:
> 
> Thiago,
> 
> I have been cleaning and building all morning. 
> 
> I keep my configure lines in a file and I haven’t been doing this since 5.8. If nothing changed, the old lines should have worked. 
> 
> I think the problem might have something to do with the OPENSSL_LIBS env var definition. I had this
> 
> OPENSSL_LIBS_DEBUG="libeay32MTd.lib ssleay32MTd.lib" OPENSSL_LIBS_RELEASE="libeay32MT.lib ssleay32MT.lib” 
> 
> and now I have been digging through the generated make files and it seems that some extra quotes were being added to the /LIBSPATH command 
> 
> I have removed them manually on the make file and tried to compiled and it compiled successfully but when I clean, configure and build again, the quotes are being added again:
> 
>  /LIBPATH:C:\Qt\5.10.0\src\qtdeclarative\lib /LIBPATH:" c:\openssl-lib-1.1\lib libcryptoMTd.lib libsslMTd.lib" C:\Qt\5.10.0\src\qtdeclarative\plugins\qmltooling\qmldbg_inspectord.lib C:\Qt\5.10.0\src\qtdeclarative\plugins\qmltooling\qmldbg_locald.lib
> 
> What do you think is adding this extra quotes?
> 
> While it was able to compile qmltestrunner after manually changing the makefile, it has now stopped on the next dependency with the same error
> 
> Thx!
> 
> Regards,
> 
> Nuno
> 
>> On 27 Oct 2017, at 16:25, Thiago Macieira <thiago.macieira at intel.com <mailto:thiago.macieira at intel.com>> wrote:
>> 
>> On Friday, 27 October 2017 04:48:15 PDT Nuno Santos wrote:
>>> Qt5Network.lib(qsslsocket_openssl_symbols.obj) : error LNK2019: unresolved
>>> external symbol _DH_get0_pqg
>> 
>> That's an OpenSSL 1.1 symbol and is only used in QtNetwork if you compile with 
>> OpenSSL 1.1 support.
>> 
>> Erase your build and configure again.
>> 
>> -- 
>> Thiago Macieira - thiago.macieira (AT) intel.com <http://intel.com/>
>>  Software Architect - Intel Open Source Technology Center
>> 
>> _______________________________________________
>> Interest mailing list
>> Interest at qt-project.org <mailto: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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/interest/attachments/20171027/2488410b/attachment.html>