I am getting MinGW64 compilation error in Qt.

yy_pc_programmer

@ChrisW67
I deleted build directory as you want.

Build project with minGw - Compile Outputs :

10:53:26: Running steps for project 1_QtTestCMake...
10:53:26: Starting: "C:\Qt\Tools\CMake_64\bin\cmake.exe" --build "D:/Qt_Udemy_Ders_Notlari/1-Udemy_Qt 6_C++_GUI_Development_Beginners_Notlarim/build-1_QtTestCMake-Desktop_Qt_6_4_1_MinGW_64_bit-Debug" --target all
[1/5 1.0/sec] Automatic MOC and UIC for target 1_QtTestCMake
[2/5 0.6/sec] Building CXX object CMakeFiles/1_QtTestCMake.dir/main.cpp.obj
[3/5 0.9/sec] Building CXX object CMakeFiles/1_QtTestCMake.dir/widget.cpp.obj
[4/5 1.2/sec] Building CXX object CMakeFiles/1_QtTestCMake.dir/1_QtTestCMake_autogen/mocs_compilation.cpp.obj
[5/5 1.4/sec] Linking CXX executable 1_QtTestCMake.exe
10:53:30: The process "C:\Qt\Tools\CMake_64\bin\cmake.exe" exited normally.
10:53:30: Elapsed time: 00:04.

and Run project ( CTRL + R ) compile output :

10:54:41: Running steps for project 1_QtTestCMake...
10:54:41: Starting: "C:\Qt\Tools\CMake_64\bin\cmake.exe" --build "D:/Qt_Udemy_Ders_Notlari/1-Udemy_Qt 6_C++_GUI_Development_Beginners_Notlarim/build-1_QtTestCMake-Desktop_Qt_6_4_1_MinGW_64_bit-Debug" --target all
ninja: no work to do.
10:54:41: The process "C:\Qt\Tools\CMake_64\bin\cmake.exe" exited normally.
10:54:41: Elapsed time: 00:00.

ChrisW67

So it builds correctly.

yy_pc_programmer

@ChrisW67
Ninja: no work to do.
(Could it have something to do with this warning?). Because the problem persists. It keeps giving build error.

JonB

@yy_pc_programmer
I do not see any build error? Indeed here I see nothing, no need to build. You might clean to remove all generated files and force a complete rebuild.

Please try to distinguish an error produced during the build process versus one which occurs when you try to run your built executable. Which is the case here for the errors you are talking about? Because I think they are runtime errors, not build (link or compilation) ones?

yy_pc_programmer

@JonB
build error persists. i don't understand this.

compile output:

16:48:11: Configuration is faulty. Check the Issues view for details.
Error while building/deploying project 1_QtTestCMake (kit: Desktop Qt 6.4.1 MinGW 64-bit)
When executing step "CMake Build"

Christian Ehrlicher

@yy_pc_programmer said in I am getting MinGW64 compilation error in Qt.:

Configuration is faulty. Check the Issues view for details.

It tells you what you have to do... fix your kit configuration.

yy_pc_programmer

@Christian-Ehrlicher @JonB @ChrisW67
I encountered the same error in Qt, I found and implemented the same here. But the result is still the same. MinGW64 error persists. Can you help me please? thanks.
+++++++++++++
Qt Forum link: https://forum.qt.io/topic/119998/the-procedure-entry-point-open-qdialog-ueaaxxz-could-not-be-located-in-the-dynamic-link-library

ChrisW67

@yy_pc_programmer said in I am getting MinGW64 compilation error in Qt.:

This line from your error message

16:48:11: Configuration is faulty. Check the Issues view for details.

What is in the Issues view?

yy_pc_programmer

@ChrisW67

11:12:20: Configuration is faulty. Check the Issues view for details.
Error while building/deploying project 1_QtTestCMake (kit: Desktop Qt 6.4.1 MinGW 64-bit)
When executing step "CMake Build"

JonB

@yy_pc_programmer
This is the same as you posted earlier. The message instructs you

Check the Issues view for details.

That is what @ChrisW67 is asking you, what is there?

yy_pc_programmer

@JonB
How can I find out what's in there?
Compile output:

13:52:36: Configuration is faulty. Check the Issues view for details.
Error while building/deploying project 1_QtTestCMake (kit: Desktop Qt 6.4.1 MinGW 64-bit)
When executing step "CMake Build"

thank you.

JonB

@yy_pc_programmer
By looking at the Issues view, like it tells you, not the compile output.

ChrisW67

@yy_pc_programmer

yy_pc_programmer

@ChrisW67 @JonB @Christian-Ehrlicher
Issues :

really thank you for asking.

ChrisW67

@yy_pc_programmer said in I am getting MinGW64 compilation error in Qt.:

OK. So your Kit definition is broken and hence disabled.

Open your Projects panel
Click the large Manage Kits button in the top left.
Look at the kit(s) you are trying to use, "Desktop Qt 6.4.1 MinGW 64-bit", on the Kits tab
- Anything flagged in red?
- Choosing the correct compiler?
- Choosing the correct Qt version (must match compiler)?
- Choosing the correct cmake tool/path?
Look at the selected Qt version on the Qt Versions tab
- Are the paths correct?
Look at the selected comiler on the Compilers tab
- Are the paths correct?

yy_pc_programmer

@ChrisW67 @JonB @Christian-Ehrlicher
I created my project on hard disk D: Does the path of this project cause problems? From what I understand, there seems to be no problem with the MinGW64 file path. I'm trying to understand my mistake. I'm taking photos so I can explain the problems to you. I am very glad that you support me. Thank you so much.

2)
3)
4)

yy_pc_programmer

@ChrisW67 @JonB @Christian-Ehrlicher
I uninstalled version 6.4.1 of Qt. I installed the old Qt 6.3.2 But again the same sound came out. Can you help me please? My projects are interrupted. How can I fix this problem?

hskoglund

Hi, try to simplify and uninstall/remove as much as possible from your PC:
remove MSVC compiler (run MaintenanceTool and uninstall MSVC)
remove Strawberry
Try to build an example project from Qt 6.3.2 MinGW in Release mode (not Debug). Does it work?

ChrisW67

Other thoughts...

Remove the WASM version of Qt also.

Recreate the project definitions:

Close out of Qt creator entirely.
Locate CMakeLists.txt.user in your source directory
Remove or rename it out of the way
Start Qt Creator
Open Project... and select your CMakeLists.txt file.

Build any better?

Do you have more then one CMake installed? Possibly getting confused.

yy_pc_programmer

@hskoglund @ChrisW67 @JonB @Christian-Ehrlicher
Unfortunately I have other projects that I'm continuing with msvc64. It is not correct for me to remove msvc64. Because my other work is affected. I ran my CMake project, which had this problem, in release mode as you said. The following problems appeared. I don't understand. Thanks.