[Development] Qt 5.9

[Alexander Nassian]

I don’t get the use case for having *only* iOS installed on my system. As well as for example only a cross Qt for an embedded device (iOS is practically the same thing). The normal development cycle should be (at least in my opinion) mainly develop on the desktop and check on the target in a regular manner. The cross build and deployment is enormously slower than on the desktop (which is ok with a cycle as I described), so why would I ever *only* use the cross build and deployment? Same thing for Android. Same thing for any embedded Linux target, but in contrast to Android and iOS we don’t deliver prebuilt binaries for them.

Beste Grüße / Best regards,
Alexander Nassian

> Am 29.11.2016 um 08:24 schrieb Jani Heikkinen <jani.heikkinen at qt.io>:
> 
>> -----Original Message-----
>> From: Development [mailto:development-
>> bounces+jani.heikkinen=qt.io at qt-project.org <mailto:bounces+jani.heikkinen=qt.io at qt-project.org>] On Behalf Of Jake Petroules
>> Sent: maanantaina 28. marraskuuta 2016 20.23
>> To: Alexander Blasche <alexander.blasche at qt.io <mailto:alexander.blasche at qt.io>>
>> Cc: development at qt-project.org <mailto:development at qt-project.org>; releasing at qt-project.org <mailto:releasing at qt-project.org>
>> Subject: Re: [Development] Qt 5.9
>> 
>> 
>>> On Nov 28, 2016, at 7:40 AM, Alexander Blasche
>> <alexander.blasche at qt.io> wrote:
>>> 
>>> Ok, let's summarize and restate the package list for Qt 5.9 based on the
>> comments provided on this mail thread. The list describes the delta to Qt 5.8
>> packages:
>>> 
>>> * For macOS we drop 10.9 and support 10.10, 10.11 & 10.12
>>> * For iOS we drop 7.x and support 8.x, 9.x, 10.x
>> 
>> * For tvOS we drop 9.x and support 10.x
>> * For watchOS we drop 2.x and support 3.x
>> 
>>> * MinGW remains 5.3 using 32 bit
>>> * Add MSVC 2017 64bit desktop
>>> * Add MSVC 2017 UWP (x64, x86, armv7)
>>> * Drop MSVC 2013 x86
>>> * Drop MSVC 2013 for WinRT/WinPhone & MSVC 2013 for WinRT 8.1 and
>> WinPhone 8.1
>>> * Drop standalone macOS Android installer; One having iOS & Android
>> 
>> As I said, let's not, and instead drop the massive macOS+iOS+Android
>> installer in favor of an iOS-only installer.
> 
> Is it really so that users of iOS installer needs only iOS binaries and nothing for desktop side? 
> 
> In this case I agree this might be the optimal solution but this doesn't decrease amount of our installers and that's why I prefer just dropping that one & keep those two old ones:
> - one just for macOS + another one for macOS, iOS & Android
> 
> br,
> Jani
> 
>> 
>>> * For Windows Android start doing Android Windows build with MinGW53
>>> * Start supporting QNX 7.0
>>> 
>>> --
>>> Alex
>>> 
>>> _______________________________________________
>>> Development mailing list
>>> Development at qt-project.org
>>> http://lists.qt-project.org/mailman/listinfo/development
>> 
>> --
>> Jake Petroules - jake.petroules at qt.io
>> The Qt Company - Silicon Valley
>> Qbs build tool evangelist - qbs.io
>> 
>> _______________________________________________
>> Development mailing list
>> Development at qt-project.org
>> http://lists.qt-project.org/mailman/listinfo/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>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20161129/5a5b0dba/attachment.html>