Qt Creator and other tools

I suggest to report that at bugreports.qt-project.org, including the contents of the log.

Installed 5.4.1 and the window is back.

Thank you p3c0. Works now.

You're welcome ! Since you have your communication working, please update the thread title prepending [solved] so other forum users may know a solution has been found :)

Thanks for posting the build sequence. I haven't tried to debug yet but the built Qt Creator seems to run. Thanks again.

Great, thanks! Stephan

Then AFAIK, it's not a setup supported by the subdirs template. Two options I can see: make a real subdirs project with all your apps and commonLib in it or treat commonLib like other dev library and have it installed in a known place and link to it the usual way

Hm, yes, in the binary installers the path is a bit different. I'm glad that you've found it. There are no plans to deprecate or remove this application, by the way.

Hi and welcome to devnet, Are you sure your target does have gdb properly installed ? And also ssh ?

Thanks for your reply. I used simple Makefiles. If I remeber correct my problem (or at least one of the problems) had to do something with python support not beeing enabled in the gdb I used. Then I just used Qt-Creator for coding and for debugging the command line gdb which worked fine for me. Maybe I will give it a try again with Qbs, but at the moment I have no project ongoing with the Ti Tiva.

Hi, I have been using Qt Creator in past, but I found it somehow unfriendly. I prefer NetBeans since I have been using it again in past, but for Java programming. Nowadays in I am coding in C++ and I prefer to stay with both NetBeans and the uniquely amazing Qt libraries. Do you know any solution? Thank you.

Turns out I can share the build settings, but they are tied to my local settings. So if I have a kit named "Qt-is-the-best" that is placed in C:\MyKit, a user that I share the project with should have the very same kit name and placed in the very same folder. So it is totally useless for my purpose.

You can also try to make a feature request for that (just check before if nobody already did)

thank you for the idea however looks it doesn't work for me if I'm adding the line #include "my_api.h" to file directly it works fine - all types and functions are highlighted and intellisense also works fine with tips for parameters but if I'm moving this line to the box of additional preprocessing code nothing works I suppose that way works for compile time only, right? and doens't affect code model at edit time? or i'm doing something wrong...

This has been fixed in the repo by now, either build from source or wait for the next release. Mac OS 10.10 was released fter the version of Qt Creator you are running. It's practically impossible to anticipate LLDB changes (or most of the other 3rd party components for that matter) before they are released.

The executable alone is not the only variable in this game, but also which kind of commands GDB is asked to perform. And this is very likely different in a Qt Creator session to what you tried to in your manual session. To see which GDB commands Qt Creator executes precisely, open Windows->Views->Debugger Log, and have a look at the left pane. You should be able to cut&paste that into a standalone gdb -i mi session, which I would not expect to react within 40 seconds either.

To use MSVC to compile Qt applications, you need to have a Qt version compiled with the same compiler, too. I suspect you might be using Qt compiled by another compiler (MinGW or other MSVC version).