Unable to find MSVS2017 compilers

[M Shajeeh Mustafa]

@SGaist yes because the error QT is giving explicitly mentions that there is some problem with the MSVS 2015 compiler. The error code once again is

'cl' is not recognized as an internal or external command,
operable program or batch file.
jom: C:\Users\shajeeh\Documents\QT\GUI Tutorials\build-T_2_basics-Desktop_Qt_5_8_0_MSVC2015_64bit-Debug\Makefile.Debug [debug\mainwindow.obj] Error 1
jom: C:\Users\shajeeh\Documents\QT\GUI Tutorials\build-T_2_basics-Desktop_Qt_5_8_0_MSVC2015_64bit-Debug\Makefile [debug] Error 2
11:26:09: The process "C:\Qt\Tools\QtCreator\bin\jom.exe" exited with code 2.
Error while building/deploying project T_2_basics (kit: Desktop Qt 5.8.0 MSVC2015_64bit)
The kit Desktop Qt 5.8.0 MSVC2015_64bit has configuration issues which might be the root cause for this problem.
When executing step "Make"

This makes me think that the claim might not be true for this case.
@koahnig If you please tell me how to compile these libraries in 2017 version. Also if I just leave it all here and start using MinGW compiler. Will it make any difference?

[SGaist]

Did you check what error your kit is showing ?

[M Shajeeh Mustafa]

As far as I interpret, the kit error is

The kit Desktop Qt 5.8.0 MSVC2015_64bit has configuration issues which might be the root cause for this problem.
When executing step "Make"

And it has configuration issues since this version is not installed in my laptop. Is there any way I can point QT to 2017 version

[jsulm]

@M-Shajeeh-Mustafa You should check what exactly the issue is: go to the kit (Tools/Options/Build & Run/Kits) and put mouse cursor over the kit - you should see a pop up containing more information.

[M Shajeeh Mustafa]

@jsulm In that window everything seems to be perfectly fine except the cMake configuration where it says "unconfigured". Any idea how to configure cMake settings? As here

[jsulm]

@M-Shajeeh-Mustafa cmake doesn't matter. Can you check the compiler on "Compilers" tab?

[OlivierDuguay]

Have you downloaded the Microsoft Windows 10 SDK ? I had a similar problem on my machine running on Windows 10 and I correct it by downloading and installing the Microsoft Windows 8.1 SDK !!! (I think there's something missing in the version for the Windows 10)

[M Shajeeh Mustafa]

@OlivierDuguay yes i have the windows 10, 8.1 and 7 sdks downloaded and installed in my system. I needed them to access directshow samples and compile them some time ago.
Also, the debugger installed in my QT (shown in debugger tab) is also from the windows 10 sdk
@jsulm I uploaded the compiler screenshot above and myself checked in the tools>options>build and run.
The compilers seem to be installed and working correctly. No issues with that. However if cMake is not a problem do you think the issue is with the compatibility with version 2017 because the compilers listed also correspond to 2015 version (but looks installed and detected automatically)
what if I just start using MinGW. Is there any issues (performance wise) with that or should I continue exploring the options for Microsoft compilers? Any suggestions

[SGaist]

Can you just re-try with your project in a path without any space ? i.e. change GUI Tutorialsby GUI_Tutotials

[M Shajeeh Mustafa]

@SGaist same result with GUI_Tutorials
I also created a new project named "Sample" and built. That too resulted in the same error.

The kit Desktop Qt 5.8.0 MSVC2015_64bit has configuration issues which might be the root cause for this problem.
When executing step "Make"

[SGaist]

Don't you have any red or yellow warning sign on the kit page ?

[M Shajeeh Mustafa]

@SGaist yes actually I have both red as well as yellow
as here

[jsulm]

@M-Shajeeh-Mustafa And what do you see if you position the mouse cursor over that warnings?

[M Shajeeh Mustafa]

@jsulm Actually I knew you would say exactly the same that's why I have already placed my cursor over my default kit (the yellow one with QT 5.8.0 MSVS 2015). The yellow box shown in the picture above is actually the output when I placed my cursor above that kit. And It shows everything perfectly fine except the CMake configuration. Which it says is un-configured.

[OlivierDuguay]

The Unconfigured C-Make is not a problem ! it is the same in my configuration but I'm able to use it anyway... Maybe if you take a screenshot of your configuration we could more easily find a solution to the problem... I remember having this sort of problem at the beginning, but I do not remember what I did to solve it.

[M Shajeeh Mustafa]

@OlivierDuguay Is this the required configuration you are asking?

If not, then how to access the configuration?