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
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 trying to drop support for it in qtwebengine in 6.7, but the problem
was it was still used for qt packaging. But if we could at least switch
packing to vs2022, it
On Monday, 5 February 2024 01:44:29 PDT Allan Sandfeld Jensen wrote:
> I was trying to drop support for it in qtwebengine in 6.7, but the problem
> was it was still used for qt packaging. But if we could at least switch
> packing to vs2022, it would mean we could drop it in QWE.
Can we commit to
> MSVC2019 and MSVC2022 is supposed to be compatible. So in theory at least
> packages made with MSVC2022 is still usable for MSVC2019 as well. It is just a
> question of which compiler we use to generate the binaries with.
That's not the case, at least according to Microsoft
On Friday, 9 February 2024 10:59:07 CET Vladimir Minenko via Development
wrote:
> 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.
->
br,
Jani
From: Development On Behalf Of Vladimir
Minenko via Development
Sent: perjantai 9. helmikuuta 2024 11.59
To: development@qt-project.org
Subject: Re: [Development] Let's drop MSVC 2019 for dev (6.8)
Hi,
I also think we should first get the 2022 compiler packages availa
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
On Tuesday, 6 February 2024 06:57:34 CET Jani Heikkinen via Development wrote:
> > How about instead we drop at an LTS+2 release? The next one is actually
> > 6.7.
> We can't switch this in 6.7 at this point anymore; we don't have packages
> for MSVC2022 at the moment and doing this (adding new
>
> How about instead we drop at an LTS+2 release? The next one is actually 6.7.
>
We can't switch this in 6.7 at this point anymore; we don't have packages for
MSVC2022 at the moment and doing this (adding new packages + removing ones)
change this late of process is too risky
br,
Jani
--
On Monday, 5 February 2024 01:39:47 PST Marc Mutz via Development wrote:
> I think we don't drop supported compilers, except in LTS+1 releases (6.9
> being the next).
I would advise you drop it before the LTS, so you don't have to keep
supporting it for however long your LTS cycle is.
How about
On Saturday, 3 February 2024 18:08:25 CET Thiago Macieira wrote:
> The compiler is pretty buggy and has several, unfixed conformance issues
> with C++.
>
> One year ago I asked on the interest mailing list about using a non-latest
> MSVC:
>
I think we don't drop supported compilers, except in LTS+1 releases (6.9
being the next).
On 03.02.24 18:08, Thiago Macieira wrote:
> The compiler is pretty buggy and has several, unfixed conformance issues with
> C++.
>
> One year ago I asked on the interest mailing list about using a
Thiago Macieira wrote in
news:2865734.Ex9A2HvPv6@tjmaciei-mobl5:
> * because our builds are labelled "msvc2019"
Does the label reflect the compiler used? (I know 2019 and 2022 are binary
compatible.)
I haven't bothered to build the most recent 5.15.x open source version, but
back at
The compiler is pretty buggy and has several, unfixed conformance issues with
C++.
One year ago I asked on the interest mailing list about using a non-latest
MSVC:
https://lists.qt-project.org/pipermail/interest/2023-January/038859.html
The reasons reported for not going to the next were:
*
14 matches
Mail list logo
