The C++ Compiler cannot run a simple test program

Daemonitas

@cristian-adam said in The C++ Compiler cannot run a simple test program:

Do you have LongPathsEnabled under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem ? As per MSDN: Maximum Path Length Limitation.

I just enabled it in Registry editor

@cristian-adam said in The C++ Compiler cannot run a simple test program:

Any special antivirus program running?

Just windows defender

@cristian-adam said in The C++ Compiler cannot run a simple test program:

moc --version

Tried to run this in cmd but it appears that i don't have it on my laptop since it said that it is not recognized as an internal or external command

@cristian-adam said in The C++ Compiler cannot run a simple test program:

cmake -S . -B build -DCMAKE_PREFIX_PATH=C:/Qt/6.5.0/mingw_64 -DCMAKE_BUILD_TYPE=Release

apparently I do not have this "CMakeList.txt." its looking for

@cristian-adam said in The C++ Compiler cannot run a simple test program:

$ cmake --build build

and this one resulted in an error too

cristian-adam

CMakeLists.txtis the project file for your CMake project.

You tried to configure the untitled6 in the wrong directory, your home directory C:\Users\-redacted-.

Make sure you go to the project:

$ d: 
$ cd "D:/programm/C++ Homework Sem 2/untitled6"
$ dir 
$ cmake -S . -B build -DCMAKE_PREFIX_PATH=C:/Qt/6.5.0/mingw_64  -DCMAKE_BUILD_TYPE=Release

cmake -S . means that CMake should look in the current directory for the CMakeLists.txt.

I assume that you have the untitled6 CMake Qt project at D:/programm/C++ Homework Sem 2/untitled6, but you can use any other project.

Regarding moc --version, where do you have Qt 6.5.0 for MinGW installed? It should be under C:/Qt/6.5.0/mingw_64/bin

The whole exercise here is to get extra information by doing things manually, step by step.

Daemonitas

@cristian-adam
alright now it shows

looks like I'm missing some packages (?)

goldenhawking

@Daemonitas Have you installed MSVC compiler together with MINGW? This picture shows that cmake try to config a MINGW Qt with MSVC 19.35.

Try to remove MSVC options from PATH, or run full-path CMAKE from Qt directory.

cristian-adam

@Daemonitas you got the part with the project directory but skipped the other steps that I've provided:

$ set PATH=C:/Qt/Tools/CMake_64/bin;C:/Qt/Tools/mingw1120_64/bin;C:/Qt/Tools/Ninja;C:/Qt/6.5.0/mingw_64/bin;%PATH%
$ cmake --version
$ ninja --version
$ gcc --version
$ moc --version

Here I'm adding CMake, MinGW GCC, Ninja and Qt 6.5.0 build for MinGW to the PATH environment variable.

Then I call the executables to make sure that they are available.

All of them should be available and provide the expected version numbers.

If you don't have moc then the path to your Qt MinGW installation is not correct, and you would need to adjust it.

When this is OK, then you can go to the project directory and issue the CMake command and build the project.

Edit: Oh, right. The CMake command had one important part missing, the Generator. Sorry about that:

$ cmake -S . -B build -G Ninja -DCMAKE_PREFIX_PATH=C:/Qt/6.5.0/mingw_64  -DCMAKE_BUILD_TYPE=Release

By default CMake would pick the Visual Studio generator and that one ignores any MinGW compiler paths 🙂

Daemonitas

@cristian-adam

Here is the entire thing
(I downloaded Qt Version 6.4.3)
Beforehand I downloaded Version 6.5.0 but I thought downgrading would do something

cristian-adam

@Daemonitas This should have worked! The tools are present, can be started, have the right versions.

What happens if you disable the real-time checking of Windows Defender?

You could try with -G "MinGW Makefiles" instead of -G Ninja as CMake generator. But this should fail in a similar way.

I assume the installation of MinGW was not corrupted, or that the system has disk failures. Something prevents the compiler to work properly.

What happens if you try it out with a hello.cpp ?

#include <iostream>

int main() 
{
   std::cout << "Hello C++ World\n";
}

with:

$ g++ hello.cpp -o hello
$ hello

If this works then the compiler is fine.

Daemonitas

@cristian-adam

Compiler is working as intended

@cristian-adam said in The C++ Compiler cannot run a simple test program:

You could try with -G "MinGW Makefiles" instead of -G Ninja as CMake generator. But this should fail in a similar way.

as for this yeah it results in an error

and disabling windows defender also didn't solve it

JonB

@Daemonitas
I am dropping in on this thread rather late, so I may be missing something. But in the example you show works you use g++ as command, why are you using c++.exe in the stuff which fails?

Daemonitas

@JonB
for the example that works I just copied what @cristian-adam told me to try out

ill try using "c++"

edit:

it also works

cristian-adam

@Daemonitas This means that the compiler is fine. Then I guess it's a CMake problem! 🤯

Qt delivers CMake 3.24.2 from Kitware, you can get a newer version from https://github.com/Kitware/CMake/tags

Unpack https://github.com/Kitware/CMake/releases/download/v3.26.3/cmake-3.26.3-windows-x86_64.zip somewhere on your disk, and use this new path for the PATH environment variable and try again from command line.

Same thing with cmake --version to make sure you have the right version.

🤞

JonB

@Daemonitas
Google for: detecting c++ compiler abi info failed (your first error message). There are quite a few hits. For example https://stackoverflow.com/questions/64438728/detecting-compiler-abi-failed-by-cmake has:

There is a CMake project simple enough but not compiling at all with Visual Studio Code.

Not same as you since you are MinGW, and that one is on Linux not Windows. But maybe there is a clue in the various hits?

What about https://stackoverflow.com/questions/48141492/cmake-with-mingw-on-windows-10-detecting-cxx-compiler-abi-info-failed, that's MinGW?

Daemonitas

@cristian-adam
So I do this right?

And this is after I disabled windows defender

cristian-adam

Rename the build directory to build-ninja and then try with -G "MinGW Makefiles".

How does it fail, similar with ABI checks?

This is bad enough to have it reported upstream at CMake https://gitlab.kitware.com/groups/cmake/-/issues

With the content of those error logs 😔

cristian-adam

As an alternative, you could open a cmd.exe and this time trying it out with Visual C++.

For this you need to to have Qt for MSVC installed at c:\Qt\6.5.0\msvc2019_64.

Then:

set PATH=C:/Qt/Tools/CMake_64/bin;C:/Qt/6.5.0/msvc2019_64/bin;%PATH%
$ cmake -S . -B build -DCMAKE_PREFIX_PATH=C:/Qt/6.5.0/msvc2019_64 
$ cmake --build build --config Release

This time no -G was passed, CMake will pick up the Visual Studio generator using msbuild.

If this works, then you'll have to change the Generator in Qt Creator's Kits configuration for the Visual C++ kit.

Edit: new cmd.exe window, so that no MinGW bits are preset in the PATH variable, CMake should pick cl.exe as before when it complained about the missing QT package.

Daemonitas

@cristian-adam
about the Visual Studio thing I also tried using the Qt extension in Visual Studio but when I tried to create a new Qt Widget Application it shows this

cristian-adam

@Daemonitas Since I'm the maintainer of the CMake bits in Qt Creator I can't say much about the Visual Studio Qt plugin. A different colleague is responsible.

Since the Visual Studio experiment from a few posts passed the ABI check, it means that at least that generator works.

If you modify the generator to "Visual Studio" in the Qt 6.5.0 MSVC Kit like this:

You should be able to to finally compile your application.

Daemonitas

@cristian-adam

Here is the result in the "General Messages" tab

cristian-adam

Since you have changed the generator in the Kit you would have to click in the Project settings on the "Re-configure with Initial Parameters" or just create a new project using this Kit.

The new project will get the right generator and should configure just fine 🙂

Daemonitas

@cristian-adam
it somehow worked (?) in a way

it enables the build and run button but at the same time it can't build when i'm using the minGw kit but when I use the MSVC kit it shows a ton of errors

as shown here

Edit:

this is the output on the MinGW kit