@Christian-Ehrlicher Thank you for clarifying!

Here the bug report for this issue: https://bugreports.qt.io/browse/QTBUG-78086

@artwaw said in QtSql Postgress MinGW8 compilation error.: I always use QtCore to avoid the plethora of single class includes. Looks like you have enough time...

There are no debug libraries in the binary folder containing the runtime used by Qt Creator (i.e. ...\Qt\Tools\QtCreator\bin. There should be under the folder for each Qt library version you have installed, and these are the libraries that your program should be built against/link to. I would guess the path should be ...\Qt\6.1.2\mingw32\lib and ...\bin (no Windows install in front of me).

@KH-219Design thank you， I‘ll try some tests.

@jsulm Yoo,thanks bro

@SGaist That was my problem. I compiled the libraries with MinGW 32 while my Qt's is MinGW 64. I changed the compiler and the problem is solved. Thanks for the help.

Hi, It's rather the other way around. Choose the most recent version of MinGW that supports what you need and then patch your version of Qt if needed to build. Beside the fact that Qt 4 has reached end of life a long time ago, you should at least move to Qt 4.8.7.

@Mixlu There are two possible issues. crypt.h is only a #include header file, needed to compile. Separately is the library containing the crypt code, which you will need at link-time (else "unresolved reference error") and/or run-time. Depending on your platform, we might be talking about libcrypt.a, libcrypt.so and/or libcrypt.dll. (For MinGW I also see mentions of libgcrypt, I don't know if that is relevant to you.) You will need one of these too, unless the crypt code is already actually in some other supplied runtime library. If you are Windows (you are, aren't you?) you might like to look at e.g. https://stackoverflow.com/questions/48410282/mingw32-compiler-giving-error-with-lcrypt

Adding "[...]/mingw73_32/bin" to PATH worked! Thank you

Are you trying to move things around in the folder where you are currently doing the application deployment ?

Hi @wimschuiteman, Peak does not distinguish between 32 and 64 bit, the library is called pcanbasic.dll in both cases. So you need to use the correct one, 32 or 64 bit, depending on your Qt architecture.

Glad you found out and thanks for sharing !

@JonB well, I thought it just creates a new build file for the new compiler (which it does), but I have to admit my understanding for compilers is not very deep.

@A-Trujillo si tu problema está solucionado, por favor no te olvides de marcar tu pregunta como tal. Muchas gracias.

@fem_dev said in Build with mingw32-make *very* slow: First Question Qt Creator starts to use jom, but I got this compile time errors: 09:35:09: The process "C: \ Qt \ Tools \ QtCreator \ bin \ jom.exe" exited normally. 09:35:09: Starting: "C: \ Qt \ Tools \ QtCreator \ bin \ jom.exe" -j4 jom 1.1.3 - empower your colors cd App / && (test -e Makefile || C: /Qt/5.15.0/mingw81_64/bin/qmake.exe -o Makefile C: /Users/VM/Desktop/rotortest/App/App.pro -spec win32- g ++ CONFIG + = debug CONFIG + = qml_debug) && C: \ Qt \ Tools \ QtCreator \ bin \ jom.exe -f Makefile C: \ Qt \ Tools \ QtCreator \ bin \ jom.exe -f Makefile.Debug 'C: \ Qt \ 5.15.0 \ mingw81_64 \ bin \ uic.exe' ../../rotortest/App/app.ui -o ui_app.h The syntax of the file name, directory name, or volume label is incorrect. jom: C: \ Users \ VM \ Desktop \ build-rotortest-Desktop_Qt_5_15_0_MinGW_64_bit-Debug \ App \ Makefile.Debug [ui_app.h] Error 1 'C: \ Qt \ 5.15.0 \ mingw81_64 \ bin \ uic.exe' ../../rotortest/App/custom_widget/value_unit.ui -o ui_value_unit.h 'C: \ Qt \ 5.15.0 \ mingw81_64 \ bin \ uic.exe' ../../rotortest/App/form/form_assembly.ui -o ui_form_assembly.h 'C: \ Qt \ 5.15.0 \ mingw81_64 \ bin \ uic.exe' ../../rotortest/App/form/form_excitation.ui -o ui_form_excitation.h The syntax of the file name, directory name, or volume label is incorrect. The syntax of the file name, directory name, or volume label is incorrect. jom: C: \ Users \ VM \ Desktop \ build-rotortest-Desktop_Qt_5_15_0_MinGW_64_bit-Debug \ App \ Makefile.Debug [ui_form_assembly.h] Error 1 jom: C: \ Users \ VM \ Desktop \ build-rotortest-Desktop_Qt_5_15_0_MinGW_64_bit-Debug \ App \ Makefile.Debug [ui_value_unit.h] Error 1 The syntax of the file name, directory name, or volume label is incorrect. jom: C: \ Users \ VM \ Desktop \ build-rotortest-Desktop_Qt_5_15_0_MinGW_64_bit-Debug \ App \ Makefile.Debug [ui_form_excitation.h] Error 1 jom: C: \ Users \ VM \ Desktop \ build-rotortest-Desktop_Qt_5_15_0_MinGW_64_bit-Debug \ App \ Makefile [debug] Error 2 jom: C: \ Users \ VM \ Desktop \ build-rotortest-Desktop_Qt_5_15_0_MinGW_64_bit-Debug \ Makefile [sub-App-make_first] Error 2 09:35:10: The process "C: \ Qt \ Tools \ QtCreator \ bin \ jom.exe" exited with code 2. Error while building / deploying project rotortest (kit: Desktop Qt 5.15.0 MinGW 64-bit) When executing step "Make" How can I fix it? My system: Qt Creator 4.12.4 (GCC based - downloaded by MSYS2) Qt 5.15.0 Windows 10 x64 Mingw-w64 jom Should be completely irrelevant. When your make file works with mingw-make, it has to work with jom as well. jomis a replacement for nmake because it did not allow -j parameter. AFAIK the MSVC does support directly multi-threading and it is not done through nmake. Besides possible side effects through parallel access to the same file or whatever, there is no difference for compilation. You are listing compile errors which are due to the compiler you are using. Second question @koahnig said in Build with mingw32-make *very* slow: Mingw-make does support now multi-threading. I did some tests back then, but after a reinstall, there was no need anymore. Are you saying that you compiled your Qt project using the default MSYS2 Mingw-64 configuration (WITHOUT jom) and got a close time compilation speed compared with MSVC 2019? Nope. I do not use MSVC 2019 compiler at all. AFAIK there was an issue with an older MinGW-make not suporting multi-threading. Therefore this discussion and the solution with jom. After my reinstall I did not bother to set up jom again. At day's end some gain is possible by switching to jom, but it was not enough to go through the hassle again. You seem to use a self-compiled Qt creator version. The output shows strange blanks around the backslashes. Possibly there is your problem with compilation.

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

finally i deleted import QtGraphicalEffects 1.0 import QtMultimedia 5.0 now it worked and built successfully . and apk file that i created. http://www.mediafire.com/download/1zcylimkzj2idu2/spiralmyappcompiled4android.apk thanks for attention

Use the "Topic Tool" button :)

Did you activate any kind of compiler optimization?

You're welcome ! Don't forget to remove the "not answered" from the title ;)