[Development] Prebuilt 32-bit versjon for MSVC 2017

[Maurice Kalinowski]

The reason we have had x86 and x64 packages for UWP is not to target those two architectures for the desktop, but rather that the x86 version also works for the emulators for Windows Phone 8 / Windows 10 Mobile as well as Windows 10 IoT (Core).

Given that two out of those are basically gone by now, I'd be fine with dropping UWP x86 packages, but keep the arm packages for out embedded user base on Windows 10 IoT.

BR,
Maurice 

> -----Ursprüngliche Nachricht-----
> Von: Development [mailto:development-
> bounces+maurice.kalinowski=qt.io at qt-project.org] Im Auftrag von Henry
> Skoglund
> Gesendet: Wednesday, February 21, 2018 2:16 PM
> An: development at qt-project.org
> Betreff: Re: [Development] Prebuilt 32-bit versjon for MSVC 2017
> 
> Hi,
> if I want to download prebuilt Qt binaries for the UWP platform then I can
> choose between 32-bit and 64-bit flavors of both MSVC 2015 and MSVC 2017.
> 
> It should be possible to offer the same variety for the Win32 versions,
> especially since I think the # of downloads for the Win32 Qt versions exceed
> the # of downloads for the UWP platform (for example, UWP requires
> Windows 10, but Win32 versions also work on Windows 7 and 8).
> 
> Rgrds Henry
> 
> 
> On 2018-02-21 14:04, NIkolai Marchenko wrote:
> > This dedication to dropping MSVC2015x32 seems quite stange after the
> > whole controversy of dropping MSVC2013 and how many people prefered to
> > tread very carefully and slowly.
> >
> > Unlike msvc 2013, 15th compiler is way better and doesn't restrain Qt
> > codebase nearly as much
> >
> > On Wed, Feb 21, 2018 at 3:44 PM, Harald Kjølberg
> > <harald.kjolberg at qt.io <mailto:harald.kjolberg at qt.io>> wrote:
> >
> >
> >     Hi,
> >
> >     Currently Qt ships with 32-bit binaries for MSVC 2015, but not for
> >     MSVC 2017. The Qt Company have received requests for adding prebuilt
> >     32-bit binaries also for MSVC 2017. By adding more prebuilt
> >     binaries, we increase the complexity, and add to the overall
> >     maintenance of our QA system. Our preferred approach would be to add
> >     binaries for MSVC 2017 and remove the binaries for MSVC 2015, as the
> >     numbers of binaries in the build remains the same. It will still be
> >     possible to manually build Qt for MSVC 2015, in the same way as it
> >     is possible to manually build for MSVC 2017 today. Feedback and
> >     viewpoints are much appreciated and will enable us to make the best
> >     possible decision.
> >
> >
> >
> >
> >     Best regards,
> >     Harald Kjølberg
> >     Product Manager - Qt for Application Development
> >
> >
> >
> >     _______________________________________________
> >     Development mailing list
> >     Development at qt-project.org <mailto:Development at qt-project.org>
> >     http://lists.qt-project.org/mailman/listinfo/development
> >     <http://lists.qt-project.org/mailman/listinfo/development>
> >
> >
> >
> >
> > _______________________________________________
> > 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