13.09.2019, 10:14, "René J. V. Bertin" <rjvber...@gmail.com>:
> I finally got around to upgrading OpenSSL and getting to work Qt 5.9 with it. 
> It
> required an additional change that I hadn't found in the 5.10 branch: 
> accepting
> the newer version during the configure phase :)
>
> https://github.com/RJVB/macstrop/blob/master/aqua/qt5-kde-devel/files/qt597/patch-openssl11-support-qt597.diff
>
> Test-driving it I did notice that the securesocketclient example would crash 
> on
> me, due to which seems to be an oversight (still present in newer code):
>
> https://github.com/RJVB/macstrop/blob/master/aqua/qt5-kde-devel/files/qt598/patch-httpsockeng-fix.diff
>
> Thiago Macieira wrote:
>
>>  On Friday, 22 March 2019 13:02:57 PDT maitai wrote:
>
>>>  Ideally qt should be compatible for both. I understand this is not
>>>  doable ?
>>
>>  It's not doable.
>
> Technically it seems that it should be possible when loading the SSL libraries
> at runtime, no?
>
>>>  At least deliver binaries for both, please.
>>
>>  That's one option we're studying, but that means you'll have to ask your 
>> user
>>  when they download.
>
> What about LibreSSL, do they have the same inter-version compatibility issues 
> as
> OpenSSL has, and could you distribute a binary version in your binary 
> packages?
> If so, it could be worth the initial investment to start supporting it?

FWIW, you can find patches for LibreSSL support at 
https://bugs.gentoo.org/562050

-- 
Regards,
Konstantin

_______________________________________________
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Reply via email to