[Development] wince and openssl

[Gunnar Roth]

My effect is that QT_NO_SSL is defined which leads to 100’s of errors.

And i did pass -openssl to configure. I patched configureapp.cpp by removing that no’s for opens and ssl ( the result i can see tomorrow)
and by the way i  think the sse2/3/4 no’s are also incorrect, i think you guys only think arm when thinking about wince.
So you also disable -sse2 flag to configure when i compile for a intel or and wec2013 platform. At least i know about this this now.
When compiling crossplatform you should trust the configure parameters.


Regards
Gunnar Roth




> Am 29.07.2015 um 18:46 schrieb Thiago Macieira <thiago.macieira at intel.com>:
> 
> On Wednesday 29 July 2015 18:17:38 Andreas Holzammer wrote:
>> 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.
> 
> I don't agree with that. Just leave the default to auto and it will change to 
> "yes" if it finds the headers. The -openssl option changes it to "yes" without 
> checking the headers, so the link may build later because it's missing 
> compiler flags.
> 
> -- 
> Thiago Macieira - thiago.macieira (AT) intel.com
>  Software Architect - Intel Open Source Technology Center
> 
> _______________________________________________
> Development mailing list
> Development at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development