How to remove autodetected debugger entry?



  • !http://i.imgur.com/8iO882y.png(Annoying)!

    As you can see, it detected the MinGW debugger but the name is all wrong. I want to be able to rename it but it won't let me. Is there anyway to rename or remove the entry? It is very annoying being labelled as MSVC2012 when it is actually MinGW.



  • For me, Creator 3.0.0 detects gdb extracted from kit Qt 5.1.1/MinGW. But that version of Qt has been uninstalled and the path listed doesn't exist. Like you, I can't edit or remove the entry.



  • You are just a few of the people having this problem. In fact, as far as I know, most Microsoft developers have the same problems. I have a feeling that there is an innuendo behind all this. What is clear to me is that Qt is not interested in providing equal easiness between Microsoft and MinGW. No, I don't think Microsoft user should use Qt. Qt is a *nix thing not a MS thing. Look. Microsoft already provides an outstanding development tool, .Net! I was also fooled by the promises of Qt. It might be that the code compiles without any problem, that is if you get a way to compile it. I would like to know if there is a way to use the Qt library, but without the "Creator" which does not create but stumps development. The reason I am asking is because I would like to know if the promises made by Qt about portability are true or just garbage like their IDE.


  • Moderators

    Hi,

    Qt Creator's GUI needs improvement for the management of kits/Qt-versions/debuggers. In the meantime, you can rename/remove the debugger entry by editing

    @C:\Users[Username]\AppData\Local\Roaming\QtProject\qtcreator\debuggers.xml@

    [quote author="ArbolOne" date="1391922129"]I would like to know if there is a way to use the Qt library, but without the "Creator"[/quote]You can integrate Qt into Visual Studio (Professional version and higher) using the VS Add-In.

    You can even build your projects from the command line if you want.


Log in to reply
 

Looks like your connection to Qt Forum was lost, please wait while we try to reconnect.