Qt Creator and other tools

You're welcome ! Don't forget to also add a unit test for the mockup object to be sure it's acting correctly. If your question is answered, please update the thread title prepending [solved] so other forum users may know a solution has been found :)

I figured out that the headers reached with F2 are the headers of the kid, while the debugger uses the path defined in Qt sources. That leads to the next question: Is it possible (and non destructive) to change the header path in the kids definition to the Qt sources?

Maybe you can help with this build issue http://qt-project.org/forums/viewthread/49203/ I'm trying to resolve an issue I have with QtSerialPort causing a crash, but I need to be able to debug into Qt (platform OSX 10.10) but I'm stuck with getting build I can use the debugger. Any help appreciated (it should lead to a critical fix in Qt :-) )

Hi, Thanks for the reply! I'll wait fix of this bug. Thanks for the link share.

I deinstalled QtCreator 3.1.1, cmake 2.8.12.2 provided by Ubuntu 14.10 repository and installed QtCreator 3.2.1 from qt-project.org. CMake was reinstalled in the meantime.

Thank you very much andrep, for the kind help. You proved right. I deleted the environment variables, uninstalled python installations and qt installation. The I reinstalled qt environment. Now I am able to trigger gdb. Thanks a lot again

Feature requests are tracked at bugreports.qt-project.org. Qt Creator Developers rarely look here.

Hi and welcome to devnet, "This":http://qt-project.org/doc/qt-5/designer-using-a-ui-file.html#a-dialog-without-auto-connect part of the documentation is what you are looking. You have described there the two possible connection technique (i.e. by hand and automatic) Hope it helps

Then just create a dialog where you can input all of that and then generate e.g. a QTextDocument that you will print

Also, if Mac OS displays it's standard message for crashing applications, please take a look at the report inside it: usually contains a nice stack and memory trace, which is mightily helpful.

These .pro files are provided by Qt. I just add to mkspec file "QMAKE_DIR_SEP = \", because there was error.

I finally got it working: I was using launchd.conf to set environment variables, which is not working with Yosemite (see http://stackoverflow.com/questions/25385934/setting-environment-variables-via-launchd-conf-no-longer-works-in-os-x-yosemite). I changed that so all my path, CC and other variables are taken into account I'm using ccache, I cleared the cache and rebuilt everything. Not sure if the launchd change or clearing ccache did the trick, but now it works - thanks.

Suddenly, my Visual Studio 2010 crashes every time I open any of my solutions (all C++). I can't pin this on the Qt installation for sure, but there's nothing else unusual I changed. Nothing I tried so far has solved this for me (delete sdf+ilk files, delete suo file, disable all extensions, unload add-ins, run in safe mode). I originally planned to use the newer Qt versions in Studio, so I installed the 5.3.2 and 4.8.6 for Studio 2010, but I have uninstalled them since. Edit: Seems to work after a reboot. That was scary.

I don't need Qt for this specific project, hence I've set the Qt Version to None in my kit (see screenshot). Thanks for the hint with the IRC channel. Will try to send a message there.

Hi, How long is the file ? What OS are you on ?

I will answer myself)) Project -> Run -> Run Environment -> Add Variable = LD_LIBRARY_PATH Value = Qt5.3.2/5.3/gcc_64/lib and it works )))

From time to time that can also be a good solution :-D

Apparently, the issue was addressed in a recent release of ccache: https://ccache.samba.org/releasenotes.html#_ccache_3_1_10 (Haven't tested it yet)

Please disregard. A restart fixed my issue.