[Development] Proposal to remove QNX 6.6 support from Qt 5.11 onwards

Tuukka Turunen tuukka.turunen at qt.io
Fri Dec 15 21:06:37 CET 2017

True. But let's discuss separately QNX 6.6 and MSVC 2013. My proposal was about QNX 6.6 specifically. Let's make sure that gets discussed even though MSVC 2013 might be a mere interesting topic for many :)

We have discussed about MSVC 2013 earlier and then some more time was desired before deciding. Perhaps enough time has passed now to open the discussion again. I do agree that complete C++11 support in all compilers is a tempting idea.



Lähettäjä: Konstantin Tokarev <annulen at yandex.ru>
Lähetetty: 15. joulukuuta 2017 21:20
Vastaanottaja: Tuukka Turunen; development at qt-project.org; James McDonnell
Aihe: Re: [Development] Proposal to remove QNX 6.6 support from Qt 5.11 onwards

15.12.2017, 22:04, "Tuukka Turunen" <tuukka.turunen at qt.io>:
> Hi,
> I propose to remove support for QNX 6.6 from Qt 5.11 onwards.
> Since Qt 5.9.0 we have supported both QNX 6.6 and 7.0, but going forward we would support only QNX 7.0 with new Qt versions. QNX 6.6 continues to be supported with Qt 5.9 LTS and Qt 5.10.
> Based on my experience QNX 7.0 is a better choice for new projects than QNX 6.6. It has, for example, better C++11 support, 64 bit support and improved graphics support.
> I have discussed the topic with James McDonnell (QNX platform maintainer) as well as QNX product management and they agree that it is better to focus into improving QNX 7.0 support with upcoming Qt releases rather that splitting the effort between QNX 6.6 and 7.0.

If we also remove MSVC 2013, only compilers with complete C++11 support on both core language
and library side will remain in CI.

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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20171215/25c83601/attachment.html>

More information about the Development mailing list