Qt Creator and other tools

I finally managed to compile... In the project, i had to add the Kit Destop (Combo Add Kit in project) (don't know why the destop autodtected doesn't work but that's fine with me if Destop works). I added my Qt Path for INCLUDE, LIBPATH AND LIB. Moreother, it seems there are changes in Qt5.0 ;-) i mean, i had to add QT+= widgets in the .pro file. QtGui/QApplication become QtWidget/QApplication and i'm just at the beginning... But, yes, QtCreator compiles something !!!YPOUOUHH WHAT A NIGHTMARE!!!!

Have fun, and happy coding :-)

[quote author="Tobias Hunger" date="1354377301"]Check the plugins: They tend to depend on several several plugins. E.g. subversion depends on TextEditor, ProjectExplorer, VcsBase and Core. Some plugins have soft dependencies as well (they will work without some other plugin, but they can't offer the full functionality). Displaying all that information will make things rather complex. I really prefer the really simple tree we have with its grouping based on functionality.[/quote] Agreed. With this complexity it is impossible to get a meaningful tree structure. Still learning. :D [quote author="sierdzio" date="1354375684"]... Since we are at it, would it not be more appropriate to move the whole Plugins menu into Tools->Options? [/quote] I would support this suggestion. When looking for the original problem, I certainly never thought of options under help. Even so I was definitely in the plugins menu already.

OK...I added a line: @QMAKE_CXXFLAGS += /MT@ The compiler warned me that it was overriding /MT with /MDd (which from the description on the MS page looks OK). My executable only grew about 1K in size, though, which has me wondering if it did indeed pick up all the needed files during compilation. Running the app on my system isn't a good test (since I have all the libraries anyway), so I guess I'll have to find a system with an older version of Windows, huh? Thanks for all the help...I think I'm at least on the right track here.

Unusual. You do have some Qt builds added to Qt Versions in options, right? Also, QtC 2.6 is released, try there - maybe it's fixed if it was a bug.

You could set up a remote linux box (Tools->Options->Devices) and configure it to connect to root@localhost. Afterwards you need to clone the kit (Tools->Options->Build & Run->Kits) you are using, replace the device type with "Generic remote linux" (don't remember the name) and the device with the one you just set up. Finally you need to add a that new kit to your project and you are done. PS: Make sure gdbserver is installed;-)

That sounds really screwed up. Do you have any designer plugins lying around somewhere which might be faulty/outdated/incompatible? You could try running designer, watching it with processmonitor or some similar tool to see what it loads/does.

That's not exactly strange, it's a very uncommon syntax. The qt syntax parser is not 100% conformant so it won't understand the more exotic constructs. That's true for almost every IDE I know of. I don't think there is a lot one can do beyond submitting a patch.

http://doc.qt.digia.com/qt/install-mac.html http://doc.qt.digia.com/qtcreator-snapshot/creator-debugger-engines.html http://doc.qt.digia.com/qt/developing-on-mac.html http://www.agile-workers.com/web/en/2012/03/qt-qmake-osx_sdk-xcode/

Thanks cincirin, it works perfectly!

Hello, just found that the solution to get STL containers debug is simply to download gdb from here http://origin.releases.qt-project.org/gdb/ and get qtcreator (2.6 in my case) to point to it in kit settings.

The Qt 4.8.4 RC4 has been just released, so 4.8.4 will be available soon.

The number is QTCREATORBUG-8331 .

Ok, it seems you have to separate extensions in the file type filter using comma instead of semicolon

I would encourage anyone reading this post to go the previous link (640) and upvote the bug. This is pretty rediculous, and I would just be sticking with Eclipse if support for the Qt integration plugin wasn't on the way out.

It works now, thanks ...

No worries, I'm not really angry ;) Your English is quite good :)