@Hjortronsylt Well libraries are simply not interchangable. Each library does hold a couple of objects defining typically the functionality given in the general naming. Some namings may have changed between Qt4 and Qt5, but not network to anything. Also when your application is requiring network functionality, but is missing it in the link process, you should see somewhere error messages. I would suggest that it is best when you are checking out examples from the tutorials. There are the network examples and there is the testlib functionality however, Qt offers more different aspects and it may make sense for you to check out those as well.

IIRC, the two builds are not using the same backend.

@Vagabond please don't forget to mark your post as solved... thanks.

I tried to investigate the issue further and figured out the following: it seems to be a problem with gdb and its disassembler when I start gdb in the console, it doesn't show me where the crash occurs, too in the debugger log, I get an error message "Disassembler failed" I tried also on another VM (Win 10, also) and a Win 7 Desktop and it works on the VM, however not on the Desktop and my first VM. I have no clue what the differences between these installations are :-( Is anyone aware of any Windows/Qt/MinGW settings that could make the disassembler fail? Thanks for any ideas, Sebastian

@JKSH said in MinGW Makefile project in QtCreator: Qt Creator does not call the compiler directly. It simply calls mingw32-make.exe and tells it which Makefile to use. mingw32-make.exe is the one that calls the compiler (g++.exe). The Makefile does not contain the absolute path to the compiler, so it searches your system environment to find g++.exe. Ah ok, it makes sense. So far, the only way might be QtCreator should add to the sys env of the shell the path of the selected compiler. But perhaps they rely on the knowledge of the users :)

@Technologist Which python and mingw version do you use?

Hi and welcome to devnet, AFAIK, the recent version of the QtWebView module uses the QtWebEngine module for Windows. Module that is not available for MinGW currently. Also you are are using a relatively old version of Qt so first thing you should update if possible to at least 5.8.

@CAD_coding form the official document, I think you can do it

@koahnig said in set<int> in Qt creator and debugger: E.g. are there conflicts through the various files holding settings? There might be, you will probably at least need to reconfigure the project's kits (i.e. deleting the *.pro.user files). I'd try to load them directly first though, it might work fine. @koahnig said in set<int> in Qt creator and debugger: The same problem there. It's the same data structure, so no surprise at all, indeed.

@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.

@Chris-Kawa Sometimes you forget to update deploy dlls, in that case runtime vs compiletime versions in "about window" would be helpful. Even if you use auto windeployqt command, you'll still need to copy other dlls (OpenSSL, etc) by hand, there you'll forget.

I can only second what @ambershark says. Using a virtual machine is far less pain than what you are trying.

Hi, Did you also install Qt for MSVC2013 ?

@raven-worx @jsulm And therefore I am looking for the way how to mangle the VCRT library into my project, it's mandatory.

I did install the one coming with the Qt package, there is no other version installed.

Did you try to run your application through debugger to see why it crashes? Any error messages?

Then it's rather QNetworkAccessManager that should be of interest.

@cemaldemir07 said: I think the solution is using x64 for more stable but not exact solution. No. If you have a bug in the 32 bit version, switching to 64 bits will not change that. You need to apply yourself, find the problem and ultimately fix it.