title: Qt Cmake configuration has no path to a C++ compiler set
body: <p>The warning I get is: "<em>Qt Cmake configuration has no path to a C++ compiler set, even though the toolkit has a valid tool chain.</em>"</p>
  
  <p>I am not sure how to change the CMake configuration so that it has a path to the compiler. I do have a C++ compiler installed as it works with VS but Qt seems to run into some problem.</p>
  
  <p>This is a screen shot of what appears as the warning: <a href="https://i.stack.imgur.com/ETET6.jpg" rel="noreferrer">https://i.stack.imgur.com/ETET6.jpg</a></p>
  
  <p>This is the error I get trying to run anything:</p>
  
  <pre><code>jom: C:\Users\User\Desktop\inv\build-Invaders-Desktop_Qt_5_8_0_MSVC2015_64bit-Debug\Makefile.Debug [debug\game.obj] Error 1
  'cl' is not recognized as an internal or external command,
  operable program or batch file.
  jom: C:\Users\User\Desktop\inv\build-Invaders-Desktop_Qt_5_8_0_MSVC2015_64bit-Debug\Makefile.Debug [debug\spaceship.obj] Error 1
  'cl' is not recognized as an internal or external command,
  operable program or batch file.
  jom: C:\Users\User\Desktop\inv\build-Invaders-Desktop_Qt_5_8_0_MSVC2015_64bit-Debug\Makefile.Debug [debug\laserbeam.obj] Error 1
  'cl' is not recognized as an internal or external command,
  operable program or batch file.
  'cl' is not recognized as an internal or external command,
  operable program or batch file.
  jom: C:\Users\User\Desktop\inv\build-Invaders-Desktop_Qt_5_8_0_MSVC2015_64bit-Debug\Makefile.Debug [debug\config.obj] Error 1
  jom: C:\Users\User\Desktop\inv\build-Invaders-Desktop_Qt_5_8_0_MSVC2015_64bit-Debug\Makefile.Debug [debug\iofile.obj] Error 1
  jom: C:\Users\User\Desktop\inv\build-Invaders-Desktop_Qt_5_8_0_MSVC2015_64bit-Debug\Makefile [debug] Error 2
  17:06:30: The process "D:\Qt\Tools\QtCreator\bin\jom.exe" exited with code 2.
  Error while building/deploying project Invaders (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"
  </code></pre>