Qt Creator and other tools

Hi, AFAIK, there's no such functionality yet (did you check the latest Qt Creator 3.1 RC) ? You can also check the "bug report system":http://bugreports.qt-project.org to see if it's already been asked, if not, you can open a new feature request

Qt still have debugging problem based on my experience. The problem here is that breakpoint symbols are not visible in the editor, this is some UI related issues as I guess. I think still it breaks at the line, hope they will fix this issue soon.

Hi and welcome to devnet ! Nice you found and thanks for sharing ! Can you also mark the thread as solved using the "Topic Tool" button ? So other forum users may know a solution has been found :) [edit: updated solved marking request SGaist]

Thanks Markus. That worked and solved the issue. Great. I'm working with Qt 4.8 and Creator 2.4.1 on a Packard Bell Easynote 10.1 with Windows 8 and MSVC 2010 Express. I installed the 8.1 SDK and therefore had to link to "c:\Program Files\Windows Kits\8.1\Debuggers\x86". Cheers R.K.

Since I' haven't received reply for a while, i've decided to try clang. I don't see much difference from the internal code formatter and clang, for the moment. I have also enabled the clang code model plugin, and again i don't see much difference.. However thanks for the reply! I'll try to look at uncrustify, it seems also to support more languages

you can run it from Qt creator Go to tools -> External -> Qt Quick -> Qt quick 2 preview(qmlscene)

Indeed the source tar file is added. Thanks.

-Do you use sessions in QtCreator and switched to the right one?-

Yep. I've seen it in my mailbox. You are quick :) Hopefully you'll get an answer there (a lot of Qt Creator developers are active there. Not so many visit the forum).

Thank you for your reply. It is just that 64 bit exe's have my preference.

Hi and welcome to devnet, You seem to be mixing Qt 4 and Qt 5. That's not possible. Also if you installed Qt through your linux distribution package manager, you don't need to build qttools yourself. They should already be installed, if not, use the package manager to get them. Hope it helps

Yes, this variant (the curly brackets on the same line with equals) works. I'm shocked... Thank you very much for your help!

Does it happen if you run qmake and make manually? You can use "warning()":https://qt-project.org/doc/qt-5/qmake-test-function-reference.html#warning-string function to trace your .pro file.

Take a look on "OUT_PWD":https://qt-project.org/doc/qt-5/qmake-variable-reference.html#out-pwd variable "Specifies the full path leading to the directory where qmake places the generated Makefile."

[quote author="andrep" date="1395863242"]Maybe related (and indicating this is not a Qt Creator problem) : https://sourceware.org/ml/gdb-patches/2014-03/msg00621.html[/quote] I've actually got a bit more data on this (posted it "here":http://stackoverflow.com/questions/15550265/qt-creator-gdb-debugging-session-ends-unexpectedly), namely: bq. The second thread is created to load my app's executable and the DLLs it requires. I've confirmed this second thread is created only when I debug my app from the Qt Creator IDE; if I run it from the IDE (i.e., use "run" instead of "debug"), or if I debug it from the command line (launch gdb from the command line), or if I run it from the command line, this second thread is never created, and the executable + DLL images are loaded by my app's main (and only) thread. On what I called "success cases" above, i.e., when this second thread exits, it exits immediately after loading the last DLL, which is why I believe this second thread is created only for this loading. Whatever is going on here, it still happens with Qt Creator 2.8.1. The reason why I think this is related to Qt Creator is that this second thread isn't spawned when I launch a debug session with dbg from the command line, only when I debug from the IDE.

Hi Billconan, This thread is more than 2 years old. Did you read the moderator's note? Please add a new topic and show us what you've tried / achieved already. Ask specific questions instead of general ones and you might get lucky. ;-)