> -Original Message-
> I'm not really remembering at the moment. The development hosts were
> already set to GCC9 for 6.0. So maybe GCC8 works, but we're not testing it
> anywhere (and that makes it basically unsupported).
Well, we're still building things on Windows with gcc 8.1. See
On 5/6/21 12:16 AM, Scott Bloom wrote:
One thing to consider here.
Visual Studio is now shipping CMake, its also getting updated for patches of a
given version of VS, and is not the same from VS 2019 or VS 2017
I know of a couple of teams that are using the VS version of CMake on windows
to
Il 05/05/21 23:27, Thiago Macieira ha scritto:
Why was that?
I'm not opposed, just wondering, because I didn't see a discussion here.
I'm not really remembering at the moment. The development hosts were
already set to GCC9 for 6.0. So maybe GCC8 works, but we're not testing
it anywhere (and
/setup app
Scott
-Original Message-
From: Development On Behalf Of Thiago
Macieira
Sent: Wednesday, May 5, 2021 14:28
To: development@qt-project.org
Subject: Re: [Development] Raising minimum CMake version to 3.16 for Qt6
On Wednesday, 5 May 2021 13:52:52 PDT Kyle Edwards via Development
On Wednesday, 5 May 2021 13:47:46 PDT Giuseppe D'Angelo via Development wrote:
> Il 05/05/21 19:58, Thiago Macieira ha scritto:
> > 3.16.0 was tagged on Nov 2019, which is a little too close for comfort.
> > For
> > comparison, we require GCC 8, which was released in May 2018.
>
> I have no idea
On Wednesday, 5 May 2021 13:52:52 PDT Kyle Edwards via Development wrote:
> CMake upstream here. We recommend always using the very latest patch
> version of CMake, since it is backwards compatible and can
> (theoretically, bugs notwithstanding) build CMake projects written for
> any earlier
On 5/5/21 1:58 PM, Thiago Macieira wrote:
3.16.0 was tagged on Nov 2019, which is a little too close for comfort. For
comparison, we require GCC 8, which was released in May 2018.
However, given that no one has apparently complained and that upgrading cmake
is far easier than the compiler, I
Il 05/05/21 19:58, Thiago Macieira ha scritto:
3.16.0 was tagged on Nov 2019, which is a little too close for comfort. For
comparison, we require GCC 8, which was released in May 2018.
I have no idea about the whole CMake situation, but FTR, qtbase/dev (or
even 6.1 already) has been bumped to
On 05/05/2021 19:58, Thiago Macieira wrote:
On Tuesday, 4 May 2021 21:51:36 PDT EXT Craig Scott wrote:
Given that we haven’t received any reports about this from user projects in
the year since the code added this constraint, and that we expect to rely
more on the metatypes going forward rather
On Tuesday, 4 May 2021 21:51:36 PDT EXT Craig Scott wrote:
> Given that we haven’t received any reports about this from user projects in
> the year since the code added this constraint, and that we expect to rely
> more on the metatypes going forward rather than less, the CMake Ports team
>
Some Qt modules rely on being able to extract metatypes from a CMake target.
That logic, implemented in the qt6_extract_metatypes() command from
Qt6CoreMacros.cmake, requires CMake behavior that was added in CMake 3.16. The
implementation of that command checks this and halts with an error if
11 matches
Mail list logo
