Il 30/11/23 11:49, Giuseppe D'Angelo via Development ha scritto:
It turns out that not every platform officially supported by Qt ships OpenSSL 3 yet. Some of these platforms are promising to maintain OpenSSL 1 for a little while longer,
Orthogonal but related, the patch kind of exposed a serious CI configuration problem: if SSL support gets accidentally disabled, the CI will still pass for a given configuration.
I guess CI configurations are simply using autodetection, and if SSL stops being detected for whatever reason (say, we break a cmake file), then the build just proceeds under QT_NO_SSL. If that's the case, should just always enforce SSL presence at Qt configure time?
(And should this enforcement be generalized to other important 3rd parties for which autotests exist? E.g. image formats.)
Thank you, -- Giuseppe D'Angelo | giuseppe.dang...@kdab.com | Senior Software Engineer KDAB (France) S.A.S., a KDAB Group company Tel. France +33 (0)4 90 84 08 53, http://www.kdab.com KDAB - Trusted Software Excellence
smime.p7s
Description: Firma crittografica S/MIME
-- Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
