Setting Visual Studio 2015 debugger
-
@Furkas Visual Studio SDK is something else. It is an SDK for developing VS extensions and it does not contain "Debugging tools for Windows". We were talking about "Windows SDK", not "Visual Studio SDK". Note that Visual Studio 2015 also installs Windows SDK, but it's a stripped down version that does not have debugging tools component. To get full Windows SDK with debugging tools component use this link.
-
Did you add it to your kit like I mentioned (don't forget to hit apply button ;) )?
Yes,
I follow and documented, with pictures, the whole installation of the Windows SDK you recommended. Then I checked "Tools -> Options -> Build & Run -> Debuggers" to make sure that Qt Creator had found the debugger and, well, yes, it did. Please have a look on the link above.
Thanks so much Chris. -
That's the debuggers tab. That's the first half of what I suggested.
I meant did you add the debugger to the kit i.e. switch to "Kits" tab, select your kit and set one of the detected debuggers there. -
That's the debuggers tab. That's the first half of what I suggested.
I meant did you add the debugger to the kit i.e. switch to "Kits" tab, select your kit and set one of the detected debuggers there. -
is this OK?
I can't tell from that picture. Click on the kit you are using in your project. The details for it will be shown below. In there there's a "debugger" combo box. If it's empty then open it, select CDB from the list and hit apply.
Btw. The list there shows Qt packages compiled for VS2012 and 2013. If you're using VS2015 none of these will work correctly. You can't mix & match VS versions.
-
is this OK?
I can't tell from that picture. Click on the kit you are using in your project. The details for it will be shown below. In there there's a "debugger" combo box. If it's empty then open it, select CDB from the list and hit apply.
Btw. The list there shows Qt packages compiled for VS2012 and 2013. If you're using VS2015 none of these will work correctly. You can't mix & match VS versions.
-
@DelNoble , @Chris Kawa
More information : i'm using W7 64b, and the 2015 has no dbg under W8. I think it's the reason of my first trouble.
I tried to load Windows SDK for W7, but the install failed.
I retry to use Qt with minGW, (my first attempt), but I'm stucked on the debug error "do not support python scripting...".
I deleted my minGW, et reloaded the latest version, carrefully installing the "mingw32_gdb_python" in the package.
But as I try to configure Qt kit with this debuger, it's marqued "Not recognised" in the type. Qt then has the error "Unable to create a debugger engine if the type "No engine"".
Where can I find a dbg runable with Qt and minGW, or, where can I find the information for a proper install ?
Thanks -
@DelNoble , @Chris Kawa
More information : i'm using W7 64b, and the 2015 has no dbg under W8. I think it's the reason of my first trouble.
I tried to load Windows SDK for W7, but the install failed.
I retry to use Qt with minGW, (my first attempt), but I'm stucked on the debug error "do not support python scripting...".
I deleted my minGW, et reloaded the latest version, carrefully installing the "mingw32_gdb_python" in the package.
But as I try to configure Qt kit with this debuger, it's marqued "Not recognised" in the type. Qt then has the error "Unable to create a debugger engine if the type "No engine"".
Where can I find a dbg runable with Qt and minGW, or, where can I find the information for a proper install ?
Thanks -
@Furkas Please don't hijack other people threads. If you want to ask about MinGW start another thread. MinGW is provided as an all-in-the-box option in the online installer for both commercial and free licenses.
-
@DelNoble The kits without exclamation marks look ok. The other two are missing a debugger (again - see the "Debugger" combo in their properties). For those just select a debugger from that combo and you should be good to go.
-
@DelNoble The kits without exclamation marks look ok. The other two are missing a debugger (again - see the "Debugger" combo in their properties). For those just select a debugger from that combo and you should be good to go.
@Chris-Kawa
Thank you Chris, it is working now. A thousand thanks and keep up the good work Chris... you're the man!! -
I'm glad I could help. If your problem is solved please mark the thread as solved from the "Topic Tools" button menu.
-
I am writing this for future reference.
Visual Studio 2015 installs Window SDK without debugger. You cannot change how it is installed at the moment of installation.
After installation you have to go to "Control Panel"->"Programs & Features" and select installed "Windows Software Development Kit". Then change the install to include debugger. -
I'm glad I could help. If your problem is solved please mark the thread as solved from the "Topic Tools" button menu.
@Chris-Kawa When we selected the Debugger in Kits tab, we also have to select the compiler.
Right now I am getting 4 options for compilers :
Which compiler should I choose in this case? -
Which compiler should I choose in this case?
Depends on what case that is. These are C and C++ compilers:
x86 - 32bit compiler producing 32bit binaries
amd64 - 64bit compiler producing 64bit binaries
amd64_x86 - 64bit cross-compiler producing 32bit binaries
x86_amd64 - 32bit cross-compiler producing 64bit binariesChoose the one you want for your project.
