[Development] MSVC 2017 32bit pre-built binaries for Qt 5.12 (replacing MSVC2015 32bit)

[Jani Heikkinen]

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 <development-bounces+jani.heikkinen=qt.io at qt-project.org> on behalf of Tony Sarajärvi <tony.sarajarvi at qt.io>
Sent: Wednesday, October 3, 2018 9:19 AM
To: Allan Sandfeld Jensen; development at qt-project.org
Subject: Re: [Development] MSVC 2017 32bit pre-built binaries for Qt 5.12 (replacing MSVC2015 32bit)

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 release
MSVC 2017 x64 - a DebugAndRelease build that's exported to release

on top of that for every qt5.git build we do an additional
MSVC 2017 x86 - a DebugAndRelease build that's _not_ exported to release

So we actually build MSVC with both 2015 and 2017 for both x86 and x64. So it's just a matter of selecting which we want to export to release.

-Tony

-----Original Message-----
From: Development <development-bounces+tony.sarajarvi=qt.io at qt-project.org> On Behalf Of Allan Sandfeld Jensen
Sent: tiistai 2. lokakuuta 2018 21.05
To: development at qt-project.org
Subject: Re: [Development] MSVC 2017 32bit pre-built binaries for Qt 5.12 (replacing MSVC2015 32bit)

On Dienstag, 2. Oktober 2018 14:47:42 CEST Alex Blasche wrote:
> Hi,
>
> We had this discussion for Qt 5.11 already but it is time to decide
> for Qt 5.12. The discussion details can be found under
>
> https://bugreports.qt.io/browse/QTBUG-63708
>
> Based on download figures and dropped MSVC2015 support for webengine
> we plan to change MSVC2015 32bit binaries over to MSVC2017 32bit. I
> realize this will not be happy news for everybody but considering the
> LTS implications of Qt 5.12 it makes sense. Nevertheless if you
> believe you have strong counter arguments please comment on the issue in Jira.
>
Would it be possible to just replace 32bit MSVC2015 with 32bit MSVC2017 on the CIs that test the individual modules, but keep both for qt5.git if we have the resources for it?

`Allan


_______________________________________________
Development mailing list
Development at qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
_______________________________________________
Development mailing list
Development at qt-project.org
http://lists.qt-project.org/mailman/listinfo/development