On Wednesday, 3 October 2018 08:26:27 PDT Shawn Rutledge wrote:
> > note that the qt(core) code is already full of QT_VERSION_CHECK(6,0,0)
> > which does effectively the same, but to activate it you would need to
> > change .qmake.conf instead of just calling configure -qt6.
>
> I’ve written
> On 2 Oct 2018, at 13:08, Oswald Buddenhagen wrote:
>
> in fact, the introduction of a respective configure feature (so you
> would #if QT_CONFIG(qt6)) has been on the table for quite a while
> already, but nobody pushed for it yet, presumably because we haven't
> officially started qt6 yet.
Hello again,
After another round of fixing (such as allowing to close issues that are 'In
Progress', because they have a different name for the transition), adding the
setting of the commit sha1 and no longer setting too many versions, we should
be live with a working bot.
I'm interested in
Hi,
Initial ones here:
https://codereview.qt-project.org/#/q/message:%22Add+changes+file+for+Qt+5.9.7%22,n,z
Please take over & finalize if needed. And get approval as soon as possible
br,
Jani Heikkinen
Release Manager
___
Development mailing list
And we don't want to increase amount of released binary packages so that's why
we will drop msvc2015 32 bit when we will start delivering msvc2017 32 bit ones
br,
Jani
From: Development on
behalf of Tony Sarajärvi
Sent: Wednesday, October 3, 2018 9:19
We currently work like this in 5.12
For all submodule builds we do:
MSVC 2015 x64 - a DeveloperBuild that isn't a DebugAndRelease build that's
_not_ exported to release
MSVC 2015 x86 - a DebugAndRelease build that's exported to release
MSVC 2015 x64 - a DebugAndRelease build that's exported to
