[Qt-interest] Configure hangs on Windows when building Qt 4.6 when adding -openssl-linked

[Gordon Schumacher]

Garth Dahlstrom wrote:
> Windows is a bit different then *nix...  configure.exe is not the same as ./configure
>   

Understood - I use both, and the method I was describing is what I'm
using on Windows (albeit with Studio).  I will admit that I do not know
which one MinGW uses, but regardless it should work with either one (I
have used similar things on Linux).

> The problem with configure.exe not parsing the OPENSSL_LIBS properly if it has spaces is bug QTBUG-2089,  I've posted a patch against 4.6.0RC1 at http://bugreports.qt.nokia.com/browse/QTBUG-2089 (though that bug needs to be reopened)
>
> The original configure.exe problem I was posting about the deadlock, has now been fixed in Git (didn't make the RC1 though): http://bugreports.qt.nokia.com/browse/QTBUG-5802
>
> Now if I could figure out how to get qmake to generate makefiles that order the libraries to link such that "-lgdi32" follows "-lssl -lcrypto" I'd be all set to have Qt built statically (atm I'm just editing the makefiles by hand).
>   

So, if you are invoking qmake yourself as I described before, you'd then
do OPENSSL_LIBS="-lssleay32 -llibeay32 -lgdi32" and you should be set.