Hi,
We can increase the test coverage (e.g. additional CI configurations) and if
needed it is possible to have the playground and other modules to be packaged
into a ‘release’ source package. Typically users are simply pulling from the
repos directly, though.
If the module is not tightly
Hi Aleix,
Comments inline.
On Thu, May 6, 2021 at 12:43 AM Aleix Pol wrote:
> On Tue, Apr 27, 2021 at 2:28 AM Chris Adams
> wrote:
> >
> > Hi Jonah,
> >
> > I'm not part of the Qt Company, so please consider my comments as
> discussion only ;-)
> >
> > I'm the maintainer of the QtFeedback
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
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 alleviate the need for another
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
>
On Tue, Apr 27, 2021 at 2:28 AM Chris Adams wrote:
>
> Hi Jonah,
>
> I'm not part of the Qt Company, so please consider my comments as discussion
> only ;-)
>
> I'm the maintainer of the QtFeedback module, at least insofar as I am willing
> to review commits and keep things building. Sailfish
We are happy to announce the release of Qt Creator 4.15 !
https://www.qt.io/blog/qt-creator-4.15-released
--
Eike Ziller
Principal Software Engineer
The Qt Company GmbH
Erich-Thilo-Straße 10
D-12489 Berlin
eike.zil...@qt.io
http://qt.io
Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni
Hi,
As mentioned on the just-published blog post [1], please register through the
Akademy registration process to be able to attend the Qt Contributors Summit.
[1] https://www.qt.io/blog/qt-contributors-summit-2021
The Akademy call for papers is now closed, but there’s plenty of space and time
13 matches
Mail list logo
