[Development] Status update on Digia's Qt for Android project

[Thiago Macieira]

On sexta-feira, 25 de janeiro de 2013 15.47.35, Eskil Abrahamsen Blomfeldt 
wrote:
> 1. What should we do about OpenSSL and our binary distributions? There 
> are legal issues related to deploying applications that contain 
> cryptographic software in some countries, so we need to find out how to 
> handle this and based on research done, we believe the APIs provided in 
> Android do not cover our needs. My idea is to have the binary 
> distribution provide both a non-SSL-enabled and an SSL-enabled build 
> (with OpenSSL built in), and the app developer will choose which to 
> download. This would be an extra burden on the app developer, though, so 
> it would be ideal if we could make the SSL-enabled library the default, 
> and just provide an option to select the other one for the use cases 
> where the legal issues come into play. Any takes? I know this issue also 
> exist for the iOS port. Does anyone know what we do with the binary SDK 
> on Windows?

The Windows SDK binary build is built with OpenSSL support, with dynamic 
loading support (the default on all platforms). That means QtNetwork will 
enable all the APIs, but will report that SSL is not supported if it could not 
find the libraries.

My recommendation is to simply ignore this issue. It's been solved before. 
Build Qt for Android with all the default options and just make sure that 
OpenSSL's headers are available during build.

Application developers who want to have SSL support will need to ensure that 
OpenSSL gets deployed alongside Qt.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.qt-project.org/pipermail/development/attachments/20130125/32e12f66/attachment.sig>