Scan for Kits can't detect different MinGW compilers if they have the same version

[pbaret]

Brief Issue Summary

When building C/C++ project on windows using MinGW compiler you have several options for a given version. Let's say I use MinGW 8.1.0 x86_64, so GCC 8.1.0 64 bits.

There are several implementation of the corresponding MinGW on windows:

• using posix or win32 thread
• using seh or sjlj exception handling

Some projects will use one or the other depending on the final target or also on the libraries they are using (if the library is built with sjlj, can't compile your program with seh exception handling).

As a consequence some people might want to put in their path for example :

• MinGW-x86_64-8.1.0-release-win32-sjlj-rt_v6-rev0
• MinGW-x86_64-8.1.0-release-win32-seh-rt_v6-rev0
• MinGW-x86_64-8.1.0-release-posix-sjlj-rt_v6-rev0

The problem is that the "Scan for kits" command only displays "GCC 8.1.0 x86_64-w64-mingw32" for each one, and because of that, in the final list of kits displayed, we only see the last one of the path (the others probably getting overridden).

Suggestion:

• separate kits from the path
• or go a little bit further in the details (for MinGW particularly as using the wrong kit can have consequences)

CMake Tools Diagnostics

No response

Debug Log

No response

Additional Information

No response

[elahehrashedi]

We are aware of this issue. Adding different compilers causes an issue on Linux. Until the time we can find a way to solve this issue for windows without causing issues in Linux, you can use this workaround. As a workaround, you can add your own kit, by making a copy of the detected kit and modifying it.

[bobbrow]

More information on adding additional kits can be found here: https://github.com/microsoft/vscode-cmake-tools/blob/main/docs/kits.md

[pbaret]

Sorry for the duplicate then and thank you for the very quick reply. Thank you also for the work around, I'll check that out.