Hello all,
FYI in this subject:
https://www.qt.io/blog/moving-to-msvc-2022-in-qt-68
--
Vladimir
On 12. Apr 2024, at 14:04, Oliver Wolff via Development
wrote:
Hey hey
On 15/03/2024 16:47, Thiago Macieira wrote:
On Monday, 5 February 2024 01:44:29 PDT Allan Sandfeld Jensen wrote:
I was
Hi,
I also think we should first get the 2022 compiler packages available for
installation in parallel to the 2019 ones. This should be available for users
for a while so that they have a transition period. Along with this, we should
announce that the 2019 compiler will be dismissed by a
Just as a reminder, the "C++20 is mandatory for users of Qt (Phase III)”
(https://bugreports.qt.io/browse/QTBUG-109362) says "The tentative plan is Qt
6.12+”
and "C++20 is required for the development and buiding of Qt itself (Phase II)”
(https://bugreports.qt.io/browse/QTBUG-109361) - "The
Hello team fluentmq,
> We would need you guys to confirm that you'd have the ressource model and the
> benefit to integrate the module to the commercial offer
I do not quite understand who exactly you expect to confirm and what you mean
with "ressource model”.
Despite that, I also think the
Hello all,
on this occasion, I would like to call the Qt Development community for
conscious and pragmatic decisions when it comes to changes in the "minimum C++
standard”.
For some reason, Qt became known to do these switches on some “surprising"
basis. I recall well as a colleague was
Hi,
I’m sorry to say, but from my perspective, this change cannot be done in 6.6. I
think 6.7 is better. And this is why.
I just had a look at the anonymous telemetry data which is sent from Qt
Creator. There is a setting for this where you can turn it on and off. So the
below numbers cover
Hello all,
I want to share on this mailing list a proposal for the timeline and phases to
support C++20 with and in Qt. Writing this, I’m aware that there were other
discussions about the support of C++20 on this mailing list. This message is a
step to get a list of features that all Qt users
