Hello Andreas,
maybe you read my mail to fast. Especially , you seem to have skipped the
>> SSL support.................no
>> OpenSSL support.............yes
>> OpenSSL support.............yes
and
> I assume this this is with -openssl passed to configure? From my reading
> of the code, that's the only possibility. Is "openssl" in your
> of the code, that's the only possibility. Is "openssl" in your
parts.
So yes i actually did pass -openssl. But as you can learn from reading my mail carefully,
this does not work out as ssl is still NO. If i remove
>> dictionary[ "SSL" ] = "no";
>> dictionary[ "OPENSSL" ] = "no";
lines then it works and i get yes for openssl and yes for ssl, when passing -openssl.
>> dictionary[ "OPENSSL" ] = "no";
lines then it works and i get yes for openssl and yes for ssl, when passing -openssl.
Andy Shaw was so kind to make a patch at gerrit
https://codereview.qt-project.org/#/c/122437/
please have a look at it.
Regards,
Gunnar
Gesendet: Mittwoch, 29. Juli 2015 um 18:17 Uhr
Von: "Andreas Holzammer" <[email protected]>
An: [email protected]
Betreff: Re: [Development] wince and openssl
Von: "Andreas Holzammer" <[email protected]>
An: [email protected]
Betreff: Re: [Development] wince and openssl
Am 29.07.2015 um 18:04 schrieb Andrew Knight:
> Hi,
>
> On 07/29/2015 06:49 PM, Gunnar Roth wrote:
>> Hi,
>> i am trying to make a wec2013 build with openssl support and got weird
>> errors.
>
> What kind of errors?
>
>> then i just found this in configureapp.cpp
>> } else if (dictionary.value("XQMAKESPEC").startsWith("wince")) {
>> dictionary[ "STYLE_WINDOWSXP" ] = "no";
>> dictionary[ "STYLE_WINDOWSVISTA" ] = "no";
>> dictionary[ "STYLE_FUSION" ] = "no";
>> dictionary[ "STYLE_WINDOWSCE" ] = "yes";
>> dictionary[ "STYLE_WINDOWSMOBILE" ] = "yes";
>> dictionary[ "OPENGL" ] = "no";
>> dictionary[ "SSL" ] = "no";
>> dictionary[ "OPENSSL" ] = "no";
>> Why is that? Why did configure not warn me?
>> Hmm ok now i found:
>> SSL support.................no
>> OpenSSL support.............yes
>> in my output... thats strange. ..
>
> I assume this this is with -openssl passed to configure? From my reading
> of the code, that's the only possibility. Is "openssl" in your
> config.summary or the contents of mkspecs/qconfig.pri?
>
>> but hmm then i saw:
>> if (dictionary["SSL"] == "auto") {
>> if (platform() == WINDOWS_RT) {
>> dictionary["SSL"] = "yes";
>> } else {
>> // On Desktop Windows openssl and ssl always have the same
>> value (for now). OpenSSL is
>> // the only backend and if it is available and should be
>> built, that also means that
>> // SSL support in general is enabled.
>> if (dictionary["OPENSSL"] == "auto")
>> dictionary["OPENSSL"] = checkAvailability("OPENSSL") ?
>> "yes" : "no";
>> dictionary["SSL"] = dictionary["OPENSSL"];
>> }
>> }
>> and i found that the default is:
>> dictionary[ "SSL" ] = "auto";
>> dictionary[ "OPENSSL" ] = "auto";
>> so fo any mkspec which start with wince ssl is set from auto to NO.
>> But why? And why is there no error when is goive openssl option to
>> configure?
>> Bug?
>
> Not necessarily, because FWICT it is just defaulting to "no" instead of
> "auto". Maybe that's just a bad default, or maybe OpenSSL is (or was)
> known to not work properly on WEC.
>
I can agree on that its just that the default is to off. You just need
to pass -openssl to configure and be good with it. Its default is to no
because a normal windows ce user does not use openssl, so its just
taking care of the normal usecase and not the cornercases. The default
would mean that every CE user will need to run the configure check if
its there, you will most likely need to pass additional include and lib
folders anyhow to configure in order to make openssl linking possible,
so its I think ok to require to pass -openssl to configure in order to
switch it on.
Thank you
Andy
--
Andreas Holzammer | [email protected] | Senior Software Engineer
KDAB (Deutschland) GmbH&Co KG, a KDAB Group company
Tel: +49-30-521325470
KDAB - The Qt Experts
_______________________________________________
Development mailing list
[email protected]
http://lists.qt-project.org/mailman/listinfo/development
> Hi,
>
> On 07/29/2015 06:49 PM, Gunnar Roth wrote:
>> Hi,
>> i am trying to make a wec2013 build with openssl support and got weird
>> errors.
>
> What kind of errors?
>
>> then i just found this in configureapp.cpp
>> } else if (dictionary.value("XQMAKESPEC").startsWith("wince")) {
>> dictionary[ "STYLE_WINDOWSXP" ] = "no";
>> dictionary[ "STYLE_WINDOWSVISTA" ] = "no";
>> dictionary[ "STYLE_FUSION" ] = "no";
>> dictionary[ "STYLE_WINDOWSCE" ] = "yes";
>> dictionary[ "STYLE_WINDOWSMOBILE" ] = "yes";
>> dictionary[ "OPENGL" ] = "no";
>> dictionary[ "SSL" ] = "no";
>> dictionary[ "OPENSSL" ] = "no";
>> Why is that? Why did configure not warn me?
>> Hmm ok now i found:
>> SSL support.................no
>> OpenSSL support.............yes
>> in my output... thats strange. ..
>
> I assume this this is with -openssl passed to configure? From my reading
> of the code, that's the only possibility. Is "openssl" in your
> config.summary or the contents of mkspecs/qconfig.pri?
>
>> but hmm then i saw:
>> if (dictionary["SSL"] == "auto") {
>> if (platform() == WINDOWS_RT) {
>> dictionary["SSL"] = "yes";
>> } else {
>> // On Desktop Windows openssl and ssl always have the same
>> value (for now). OpenSSL is
>> // the only backend and if it is available and should be
>> built, that also means that
>> // SSL support in general is enabled.
>> if (dictionary["OPENSSL"] == "auto")
>> dictionary["OPENSSL"] = checkAvailability("OPENSSL") ?
>> "yes" : "no";
>> dictionary["SSL"] = dictionary["OPENSSL"];
>> }
>> }
>> and i found that the default is:
>> dictionary[ "SSL" ] = "auto";
>> dictionary[ "OPENSSL" ] = "auto";
>> so fo any mkspec which start with wince ssl is set from auto to NO.
>> But why? And why is there no error when is goive openssl option to
>> configure?
>> Bug?
>
> Not necessarily, because FWICT it is just defaulting to "no" instead of
> "auto". Maybe that's just a bad default, or maybe OpenSSL is (or was)
> known to not work properly on WEC.
>
I can agree on that its just that the default is to off. You just need
to pass -openssl to configure and be good with it. Its default is to no
because a normal windows ce user does not use openssl, so its just
taking care of the normal usecase and not the cornercases. The default
would mean that every CE user will need to run the configure check if
its there, you will most likely need to pass additional include and lib
folders anyhow to configure in order to make openssl linking possible,
so its I think ok to require to pass -openssl to configure in order to
switch it on.
Thank you
Andy
--
Andreas Holzammer | [email protected] | Senior Software Engineer
KDAB (Deutschland) GmbH&Co KG, a KDAB Group company
Tel: +49-30-521325470
KDAB - The Qt Experts
_______________________________________________
Development mailing list
[email protected]
http://lists.qt-project.org/mailman/listinfo/development
_______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
