Thanks for all the replies so far. Seems this is not a topic where people
working on Qt have (already) opinions or ideas about or at least some to share
:)
Guess this needs to wait until there are more 3rd-party QCH files in the wild
obviously, so the issues get more important and there is
On quarta-feira, 30 de novembro de 2016 07:53:40 PST Jake Petroules wrote:
> How about we have one package per host platform which includes all possible
> hosts and targets compatible with it? Then we have 3 packages, ever.
Or, at least, one binary per platform + compiler combination. So that's 1
On quarta-feira, 30 de novembro de 2016 07:35:25 PST Jake Petroules wrote:
> I think you're forgetting WinRT? Also 2015 x86+x86_64+armv7 + 2013 x86 +
> armv7(phone), making 11.
Right, I was.
Can anyone find out from the traffic stats if people actually download those
things?
--
Thiago
We are happy to announce the release of Qt Creator 4.2 RC1:
https://blog.qt.io/blog/2016/11/30/qt-creator-4-2-rc1-released/
Br,
--
Eike Ziller
Principal Software Engineer
The Qt Company GmbH
Rudower Chaussee 13
D-12489 Berlin
eike.zil...@qt.io
http://qt.io
Geschäftsführer: Mika Pälsi, Juha
> Then let's not drop the 32-bit mingw. But we should add the 64-bit one, and if
> possible to 5.8 too.
The deal is that we don't want to increase the number of packages
in total.
Personally, I don't see the qualms with switching to 64 bit for MinGW
instantly. For MinGW, there are hardly
