Hi Everyone!
We have branched '6.2.3' from '6.2' now. So from now on all changes targeted to
Qt 6.2.3 release must have 'Pick-to: 6.2.3'. And like usual staging in '6.2.3'
will be restricted to release team only and only release blocker fixes (+
documentation updates) will be taken in.
Target
On Monday, 10 January 2022 07:28:11 PST Edward Welbourne wrote:
> Presumably we have a tool - automoc ? - that scans our source to
> determine which headers need to be moc'd and which resulting moc output
> isn't already #include-ed, so needs separate compilation. We can surely
> adapt that tool t
On Monday, 10 January 2022 06:02:43 PST Thiago Macieira wrote:
> The only problem is if you do the above, then you don't have qmake and you
> can't build qmake-based projects against your Qt build. You can get away
> with using the other build's qmake and then changing LD_LIBRARY_PATH to
> point to
This is now DONE
From: Heikki Halmet
Sent: Monday, January 10, 2022 17:18
To: Ville-Pekka Karhu ; Qt development mailing list
Subject: RE: Monthly CI maintenance break - January (Mon 10th Jan 2022)
Hi,
Unfortunately maintenance break is still ongoing. We hav
Thiago Macieira (3 January 2022 15:10) wrote
[Referring back to unity builds.]
> Anyway, while this is great for reducing the number of build files,
> it's not a complete solution. It does point to one simple thing we
> should all do: includemoc. I think I've kept QtCore this way: all .cpp
> #inclu
Hi,
Unfortunately maintenance break is still ongoing. We have some issues which CI
team is trying to resolve as quick as possible.
Br
Heikki
From: Development On Behalf Of Ville-Pekka
Karhu
Sent: maanantai 10. tammikuuta 2022 8.06
To: Qt development mailing list
Subject: Re: [Development] Mo
On Monday, 10 January 2022 00:10:54 PST Eike Ziller wrote:
> Accept that, and open the toplevel Qt project. Should work fine, and
> _because_ CMake does not recursively create subprojects, the incremental
> build with Ninja is very fast on the whole project. No recursive make
> involved.
Unless yo
Hi!
qmake actually creates a “subproject” per sub-.pro file, and these “subproject”
can be opened, built, run separately.
CMake works different, a build only consists of a single “project”, so it is
not possible to open “subprojects”.
The options, as I see them:
Accept that, and open the topl
Gerrit maintenance break is now over.
From: Development on behalf of Jukka
Jokiniva
Date: Monday, 10. January 2022 at 8.35
To: qt-dev
Subject: Re: [Development] Codereview scheduled maintenance break on Monday
10-Jan 7 am CET
Gerrit maintenance break starts now.
From: Development on behalf
