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

Garth Dahlstrom ironstorm at gmail.com
Sun Nov 22 19:02:57 CET 2009


Hi Gordon, 

Windows is a bit different then *nix...  configure.exe is not the same as ./configure

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).

Cheers,

-G


On 2009-11-22, at 11:19 AM, Gordon Schumacher wrote:

> Garth Dahlstrom wrote:
>> On 2009-11-12, at 9:07 AM, Zeljko <zeljko at holobit.net> wrote:
>> 
>> 
>>> Garth Dahlstrom wrote:
>>> 
>>> 
>>>> windowsmobile -debug-and-release -openssl-linked -I "E:\OpenSSL
>>>> \include" -L "E:\OpenSSL\lib\MinGW"
>>>> 
>>> what about (path delimiter change),
>>> windowsmobile -debug-and-release -openssl-linked -I "E:/OpenSSL
>>> /include" -L "E:/OpenSSL/lib/MinGW"
>>> 
>> 
>> Tried it with slashes in both directions, it even hangs if I delete  
>> the -I & -L args and just have "-openssl-linked"...   I've tried this  
>> on 3 Windows XP VMs result are the same on each.   Longest I left it  
>> running was about 6 hours.
>> 
>> It is definitely something to do with "-openssl-linked" specifically  
>> causing configure.exe to hang.
>> 
>> I also tried " -openssl-linked OPENSSL_LIBS='-lssleay32 -llibeay32' "  
>> but configure.exe spits out the help page telling me that is not a  
>> correct syntax.
>> 
> 
> And it's right - those are qmake vars, not configure options.  In order
> to do it that way (and that is what I am doing, for my typical reason of
> doing some unusually complexicated stuff) you need to pass the
> "-no-qmake" option to configure, and when it completes issue something like:
> 
> bin\qmake -r projects.pro OPENSSL_LIBS="-lssleay32 -llibeay32"





More information about the Qt-interest-old mailing list