[Interest] Problems building Qt 5.8 from source with openssl-linked Windows

[Nuno Santos]

Hi,

I'm trying to build Qt 5.8 from source on Windows with openssl-linked 
support with the following configure line:

configure -confirm-license -recheck -prefix 
c:\qt\5.8\msvc2013_5_8_static_32 -commercial -debug-and-release -static 
-static-runtime -openssl-linked -I c:\openssl-lib\include -L 
c:\openssl-lib\lib OPENSSL_LIBS_DEBUG="ssleay32MTd.lib libeay32MTd.lib" 
OPENSSL_LIBS_RELEASE="ssleay32MT.lib libeay32MT.lib"

However, it seems to be ignoring the -I and -L parameters as it is 
failing during compilation because it can't find opensll/ssl.h which is 
there. Analysing the compiler output I can see that the -I and -L are 
not being passed to the compiler:

cl -c -FIqt_pch.h -Yuqt_pch.h -Fp.pch\debug\Qt5Networkd_pch.pch -nologo 
-Zc:wchar_t -FS -Zc:strictStrings -Zc:throwingNew -Zi -MTd 
-D_HAS_EXCEPTIONS=0 -GR -W3 -w34100 -w34189 -w44996 -w44456 -w44457 
-w44458 -wd4577 -wd4467 /Fd..\..\lib\Qt5Networkd.pdb -DUNICODE -DWIN32 
-DQT_NO_USING_NAMESPACE -DQT_NO_FOREACH -DWINVER=0x0600 
-D_WIN32_WINNT=0x0600 -DQT_USE_SYSTEM_PROXIES -DQT_BUILD_NETWORK_LIB 
-DQT_BUILDING_QT -D_CRT_SECURE_NO_WARNINGS -D_USE_MATH_DEFINES 
-DQT_NO_CAST_TO_ASCII -DQT_ASCII_CAST_WARNINGS -DQT_MOC_COMPAT 
-DQT_USE_QSTRINGBUILDER -DQT_DEPRECATED_WARNINGS 
-DQT_DISABLE_DEPRECATED_BEFORE=0x040800 -DQT_CORE_LIB -DQT_CORE_LIB 
-DQT_NO_EXCEPTIONS -I. -I..\3rdparty\zlib -Ikernel -I..\..\include 
-I..\..\include\QtNetwork -I..\..\include\QtNetwork\5.8.1 
-I..\..\include\QtNetwork\5.8.1\QtNetwork -Itmp 
-I..\..\include\QtCore\5.8.1 -I..\..\include\QtCore\5.8.1\QtCore 
-I..\..\include\QtCore -I.moc\debug -I..\..\mkspecs\win32-msvc 
-Fo.obj\debug\ 
@C:\Users\nsantos\AppData\Local\Temp\qhttpnetworkconnection.obj.8440.141.jom
qhttpnetworkconnection.cpp
c:\qt\5.8\src\qtbase\include\qtnetwork\5.8.1\qtnetwork\private\../../../../../src/network/ssl/qsslcontext_openssl_p.h(60): 
fatal error C1083: Cannot open include file: 'openssl/ssl.h': No such 
file or directory

I have tried to add OPENSSL_PATH="c:\openssl-lib\include" but didn't 
made any difference.

I'm wondering if the way this is passed to configure has changed. Any ideas?

Thanks!

Regards,

Nuno