Hi Thiago, I would not take the silence as a sign of consent. I rather have the impression that there is no sufficient interest in this at the moment. Despite this, there are quite a few urgent improvements required on the CI. I greatly doubt it will be possible to have additional configurations for any of the permutations of conditions you might need.
-- Vladimir Minenko vladimir.mine...@qt.io +49 171 90 61 461 Product Lead for Qt Foundations, mobile and desktop platforms The Qt Company GmbH - https://qt.io On 18. Oct 2024, at 17:36, Thiago Macieira <thiago.macie...@intel.com> wrote: On Monday 14 October 2024 10:31:22 GMT-7 Thiago Macieira wrote: On Monday 14 October 2024 09:53:56 GMT-7 Thiago Macieira wrote: The last time we discussed this was at QtCS24 (https://wiki.qt.io/QtCS2024_C%2B%2B20), where IIRC the conclusion was that ATM, there is no reason to switch to C++20. So, it is definitely not in 6.9. That was "not require C++20 for users". I'm not asking for that. I am asking that we switch how we build Qt. Users won't be affected. And no platforms will be dropped, no new compilers will be required. That was Phase I½ in the QtCS link above. What's the drawback with this? I'm going to assume that silence is consent to "there is no drawback" and will proceed with the implementation. -- Thiago Macieira - thiago.macieira (AT) intel.com Principal Engineer - Intel DCAI Platform & System Engineering -- Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
-- Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
