I agree with this. There are binary incompatibilities between 0.9 and 1.x, and we haven't found all of them. Before 1.0, openSSL didn't clearly separate internal data structures from its API. As a result the existing Qt openssl codebase is using some internal data structures which causes subtle errors when using a different openssl version to what it was compiled against.
(of course, we should fix these issues wherever possible by using the public API of openSSL) Unfortunately it's usually our users that are finding these problems when using the windows binary packages. Linux users are rarely affected, as they more often use source builds or distro provided binaries that are compiled against the distro provided openssl packages. If there are no objections, lets update the documentation and make sure the binary packages for the next release are using it. On 31 July 2013 11:26, Peter Hartmann <phartm...@blackberry.com> wrote: > On 04/16/2013 01:19 PM, Richard Moore wrote: > > 2) We could say 1.0.0 is the minimum. > > *bump* So is everybody fine with this? Also, does somebody from the > release team know whether Windows / Linux packages are built with > version 1.0.*? > > If yes, we could go ahead and change e.g. > http://qt-project.org/doc/qt-4.8/requirements.html or > http://qt-project.org/doc/qt-4.8/supported-platforms.html, saying > OpenSSL 1.* is officially supported, and patches for 0.9.8* are accepted > or so. > > I think we should not hold on to 0.9.* forever though, because when > version 1.1.0 comes along (no idea when that will be) we will have to > deal with binary compatibility breakages again, and handling 3 different > interfaces will be quite a bit of work. > > Peter > > > --------------------------------------------------------------------- > This transmission (including any attachments) may contain confidential > information, privileged material (including material protected by the > solicitor-client or other applicable privileges), or constitute non-public > information. Any use of this information by anyone other than the intended > recipient is prohibited. If you have received this transmission in error, > please immediately reply to the sender and delete this information from > your system. Use, dissemination, distribution, or reproduction of this > transmission by unintended recipients is not authorized and may be unlawful. > _______________________________________________ > Development mailing list > Development@qt-project.org > http://lists.qt-project.org/mailman/listinfo/development >
_______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development