[Development] Dropping MinGW support in Qt 6 (Was: HEADS-UP: QStringLiteral)
henry at tungware.se
Wed Aug 21 23:33:15 CEST 2019
Nice. Those .exe files would be closer to 30 MB than 20 MB, right? But
nowadays that kind of sizes are quite common/normal and does not incur
any noticeable delays when launching them.
Building static Qt apps this way for Windows I think will be more
popular. I wish Qt would include a static building wizard, like showing
say the most common static build flavors as check boxes, and perhaps a
detailed view for cherrypicking exactly what modules you want.
On 2019-08-21 23:10, Ola Røer Thorsen wrote:
> ons. 21. aug. 2019 kl. 20:54 skrev Henry Skoglund <henry at tungware.se
> <mailto:henry at tungware.se>>:
> I've switched from VS to MinGW, the #1 reason: I can distribute an
> file which is runnable directly on the user's desktop (no
> This is *verboten* when using VS, you have to send along the
> distribution dlls (ucrtbase.dll etc.) and install them.
> Agreed. I cross-build completely statically linked Qt quick apps on
> Linux using mingw-w64 and share them (.exe only, no DLLs) to
> colleagues who only run windows. Very useful! So I would not vote for
> requiring MSYS2 or similar if it would mean the end of cross building
> Windows apps on Linux (if I've understood what MSYS2 is correctly).
> I would not however mind upgrading the compiler/toolchain if my
> particular one was too old for some future Qt version.
> Development mailing list
> Development at qt-project.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Development