Unable to create a debugger engine of the type "No engine"
I had similar issue when I installed Qt 5.8.0 having QtCreator 4.2.1 inside it.
I did not have Visual Studio 2015 installed on my machine, and I didn't want to install Visual Studio 2015 for it. So I installed visualcppbuildtools_full from microsoft website, which installed all the required compiler. QtCreator detected the MSVC compilers.
Still QtCreator complained about debugger. For that, I downloaded Windows SDK 10 stand alone with only Debugging Tools as selected. And installed the Debugging tools, which resolved the debugger issue also.
To cross check,
- Verify whether C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\cdb.exe and C:\Program Files (x86)\Windows Kits\10\Debuggers\x86\cdb.exe are created with all other binaries.
- Now, open QtCreator. Go to Tools | Options | Build & Run | Debugger tab.
- Verify above cdb.exe files paths are listed under Auto-detected section.
Debugging starts working after this.
Unable to create a debugger engine of the type "No engine"
This is a bug in Q1t Creator 3.3.0, if you update, you should be OK. Alternatively, it seems solvable by updating to Python 2.7.1.
The application failed to initialize properly (0xc000007b)
If Qt is 32bit, so does the Python.dll
ImportError: No module named site
This seems to be a Python configuration problem as discussed here: Python (Windows) - ImportError: No module named site
Setting the PYTHONPATH / PYTHONHOME variables
Right click the Computer icon in the start menu, go to properties. On the left tab, go to Advanced system settings. In the window that comes up, go to the Advanced tab, then at the bottom click Environment Variables. Click in the list of user variables and start typing Python, and repeat for System variables, just to make certain that you don't have mis-set variables for PYTHONPATH or PYTHONHOME. Next, add new variables (I did in System rather than User, although it may work for User too): PYTHONPATH, set to C:\Python27\Lib. PYTHONHOME, set to C:\Python27.
Alternatively, installing Python 2.7.1 seems to fix that too.