[Development] Qt 5.9

André Hartmann andre.hartmann at iseg-hv.de
Fri Nov 25 16:33:01 CET 2016


Hi,

This nice thing about the MinGW package is, that you get Qt, Creator, 
the compiler and the debugger in one package. I already recommended this 
package to people that wanted to start Windows development and this 
always worked fine.

So another +1 for MinGW 32bit build from my side.

Andre

PS: And I never want to got back to early Creator 2.x times, when you 
had to put all this together your own, and the requirements changed for 
every new Creator version...

Am 25.11.2016 um 09:39 schrieb Eric Lemanisser:
> We have been using the MinGW binaries of Qt for years in production
> without problems. Until now 64bit has not been required, so we only used
> 32bit which is able to run on all windows platforms. A non-negligible
> part of users are using 32bit windows (on tablets for example), so it
> does not seem a very good move to stop offering MinGW 32bits. That said
> we would definitely make use of MinGW 64bits binaries !
>
> Eric Lemanissier
>
> Le ven. 25 nov. 2016 à 08:03, Bo Thorsen <bo at vikingsoft.eu
> <mailto:bo at vikingsoft.eu>> a écrit :
>
>     Den 23-11-2016 kl. 23:10 skrev Thiago Macieira:
>     > On quarta-feira, 23 de novembro de 2016 21:14:52 PST Simon Everts
>     wrote:
>     >>> That is not relevant here. I am using Windows 10 (64-bit) but I
>     am still
>     >>> forced (because of 3rt-party-libraries) to develop
>     32-bit-Qt-applications.
>     >>> Even if the operating system is 64-bit there can be a lot of 32-bit
>     >>> application, e.g. VS 2013 and VS 2015 are still 32-bit applications.
>     >>
>     >> +1
>     >>
>     >> As a machine manufacturer we are still deploying 32bit windows
>     systems
>     >> because of this reason. We'll be on 64bit windows soon, but need
>     to support
>     >> the 32bit systems for at least 5 years. A lot of industrial computer
>     >> suppliers still install 32bit images on computers because there
>     aren't any
>     >> 64bit drivers available for the hardware.
>     >
>     > Good, thanks for the information, Simon and Helmut.
>     >
>     > I know the sample size here is horrible, but in your opinion what
>     compiler
>     > should we keep offering a 32-bit binary build for?
>     >
>     > MSVC 2013
>     > MSVC 2015
>     > MinGW
>
>     The reason for doing 32 bit MSVC releasees is 3rd party libraries. Is
>     that a valid reason for MinGW? I would have thought that the guys using
>     it pretty much have to compile everything themselves anyway.
>
>     I don't know, though. I won't ever use MinGW myself unless a customer
>     forces me to.
>
>     Bo Thorsen,
>     Director, Viking Software.
>
>     --
>     Viking Software
>     Qt and C++ developers for hire
>     http://www.vikingsoft.eu
>     _______________________________________________
>     Development mailing list
>     Development at qt-project.org <mailto: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
>


-- 
Best regards / Mit freundlichen Grüßen
André Hartmann, Dipl.-Ing. (FH)
Software Project Manager

iseg Spezialelektronik GmbH         |  phone: ++49 (0)351 26996-43
Bautzner Landstr. 23                |  fax:   ++49 (0)351 26996-21
D-01454 Radeberg / Rossendorf       |  web:   www.iseg-hv.com

Geschäftsführer / Managing director: Dr. F. Gleisberg, Dr. J. Pöthig
Amtsgericht / Lower district court: Dresden HRB 16250
Ust.-Id.-Nr. / VAT-ID: DE812508942

Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
Informationen. Wenn Sie nicht der richtige Adressat sind oder
diese E-Mail irrtümlich erhalten haben, informieren Sie bitte
sofort den Absender und vernichten Sie diese Mail.
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser
Mail ist nicht gestattet.

This e-mail may contain confidential and/or privileged information.
If you are not the intended recipient (or have received this e-mail
in error) please notify the sender immediately and delete this e-mail.
Any unauthorized copying, disclosure or distribution of the material
in this e-mail is strictly forbidden.



More information about the Development mailing list