Qt MinGW 64-bit

mrjj

well they also stopped making a 32 bit linux. It all depends on download stats
etc and the huge cost of making pre-compiled.

mingw is always treated a bit as the stepchild (from all)
as most projects is using visual studio and its de facto standard for windows development.
Also the new web engine stuff is NOT supported in mingw.

So it makes more sense to focus on 32/64 for VS for PRO development and
mingw for the more casual and works out of the box experience.

But yes, it might come. Like 32 out and only 64 bit.
Most new windows are 64 bit and xp is finally dying.

koahnig

@satysin

I do not know anything about the release plans for a 64 bit version.
I believe the choices for 64 bits are too many. I think there has been an extended discussion in the past.

From development point I was not convinced that it is a good idea to continue with 64 bit MinGW version. I was a bit surprised when I had noticed that at that time it was slower especially when debugging. However, that have been because of machine limitations. The debug versions were relatively large. Presumably I could tweak the parameters for speeding up. Anyway, as long as I do not see a real need, it does not make sense to switch for me.

satysin

@mrjj Yes I guess I should just go with MSVC then. I have Visual Studio 2017 RC installed but currently the Qt installer does not detect it, I assume this is because they do not have a Qt build for it yet.

mrjj

@satysin

Yes. The Qt must match the VS version. ( due to DLL loading)
I think VS2015 is the newest. ( didnt check)

Its not very hard to compile qt with minge 64 but it does take long time.

koahnig

@satysin

When go MSVC, make sure that can install a compatible, pre-compiled version of Qt libs. Otherwise you have to do a compilation yourself as well.

satysin

Thank you all. I have marked as solved.

SGaist

Hi and welcome to devnet,

Certainly not with 5.8. However there was a thread talking about that here.

As to why there was not yet a MinGW64, the answer is always the same: it's about manpower and hardware.

The CI has its limits and is already under heavy pressure building Qt for the 5.6 to 5.8 branches as well as dev. Each pre-built package is also tested. For Windows alone it means 5 different versions to generate and test.

satysin

@SGaist Yes I can understand the difficulties in supporting yet another build. Also with MSVC now being "free" for open source projects (with Visual Studio Community) I guess it means MinGW will see a drop in users going forward.

SGaist

Not necessarily, some people prefer to stay with OpenSource Tools and keep the same compiler as much as possible.

Also, to get started with Qt on Windows, the MinGW build is ideal since it doesn't require to go somewhere else for additional downloads and setup like Visual Studio does. You just have to select MinGW in the additional software in the installer. Furthermore, it's only been recently that the C++ tools can be downloaded independently, otherwise you had to install the whole of VS just to get the compiler and you also need to install the debugging tools separately. And by whole of VS, you also have to be sure to check C++ otherwise it's installed without it.

And from a compatibility point of view, the various versions of VS are not compatible with each others so you always have to ensure that you have all C++ dependencies built correctly.

yigene

32bit could crash when it reach to 4GB memory right

don't like that as we have some vendor products which is 32bit and then the process crash when it reach to 4GB memory!

mrjj

@yigene

Well anything can crash when it runs out of memory
and the app is not programmed correctly to handle it.
So if you run a 64 bit app on 32 bit OS with 1 GB ram it could just as easy crash as 32 bit version.

jsulm

@yigene To add to @mrjj : does your app need that amount of memory? If not and it does not have memory leaks than there is no real reason to have it as 64bit.