Bump!
Same problem here!
Project structure:
project.pro (main pro file)
tools.pri (in tools subfolder)
gui.pri (in gui subfolder)
project.pro ( http://paste.ubuntu.com/9279754/ )
tools.pri ( http://paste.ubuntu.com/9279756/ )
gui.pri ( http://paste.ubuntu.com/9279762/ )
All the files specified inside the .pri files are inside the respective folders. Only with the $$PWD prefix the files are shown inside QtCreator (so in the above pasted files, only the gui/about.h file is shown, screenshot: http://i.imgur.com/V6fnGwL.png ).
An interesting note: The invisible files can be accessed using the Ctrl+Click technique when viewing the .pri file from inside the QtCreator, so something is fishy.
Do you use second project as a shared library?
Try to put break point immediately before calling a function from project2 and then create breakpoint in that function. Does it work?
SOOOO I got it.
I had
CMAKE_PREFIX_PATH
set to
C:\Qt\Qt5.3.1\5.3\msvc2013_64_opengl
I simply deleted that environment variable and now it works.
I don't think this is intended behavior. It should be possible to set all variables in CMake and override whatever is in CMAKE_PREFIX_PATH.
My problem that I don't see what exactly the makefile is doing. SO far I do not like QtCreator.
I mistakenly assumed that you need a filter messages in your application. Then "qInstallMessageHandler":http://qt-project.org/doc/qt-5/qtglobal.html#qInstallMessageHandler would be useful.
But it does not help to filter the application messages in QtCreator.
In QtCreator project setting, run configuration you can select custom executable.
On Linux development host you can create a script that will start your app and then filter out all unnecessary messages.
I have not tried to use QtCreator for android development yet so don't know if start app through a script will work for android.
So this is not the ideal way to correct the issue but here is my workaround:
open up the offending applications at a "safer" resolution--one much smaller than the maximum available. Start the offending applications, and you should observe no issues. Uping the resolution should then be possible without problems. I used 1024x768 as my safe resolution to get up to 1920x1080.
For multi-virtual monitor setups, you may also need to reorder the monitors in Display Preferences so that display 2 is on the left and display 1 is on the right--the opposite of default. At this point, upping both displays to the correct resolution was possible without the cycle spasms described in the original post.
Yep, it works now.
I unchecked "Always use the QML emulation layer provided by Qt Creator". After that, QtDesigner built a new and working qml2puppet layer. Thank you very much, again!
Greetings to Berlin,
Frime
The problem can be solved building GDB with a Python 2.7 or 3 in path. Python 2.6 from Centos 6.X lacks some feature which breaks the debugger integration for Qt Creator 3.1.2.
Python 2.6 could also break the debugger pretty printers for Qt Creator > 2.8.1 and < 3.2, but I haven't tested any other version than 2.8.1 and 3.1.2.
More info in can be found in QTCREATORBUG-13462.