Qt Creator and other tools

Hi, It seems to be what I want. Thank you! Regards, Norbert

@ziller said in QtCreator 4.2 - CMake ROS project: Exactly that all projects that use that kit get this setting for CMAKE_PREFIX_PATH :) I know that... What I want to know is what could be wrong removing %{Qt:QT_INSTALL_PREFIX} from the path.

AFAIK, macOS and Linux behaviour are the same qmake wise. When going command line (or setting up the CI) I always use out of source builds, this avoids surprises when testing different build types.

Good Then since the issue is solved for you please mark the thread as such using the "Topic Tools" button :)

@bladekel Hi Did you try as full kit ? as @koahnig says ? http://doc.qt.io/qtcreator/creator-targets.html

To add to @koahnig, yes you are doing a wrong mix, if you are using VS2015 you should install the debugging tools from Microsoft.

Hi and same to you ! Start Qt Creator with gdb and you'll be able to get a stack trace. Or have your own build of Qt Creator that you start from another instance of Qt Creator ;)

@koahnig OK Just started the installer as root. The installation directory is /opt/Qt/ Before I start it, I must to change it to can it execute. I did this in Midnight Commander. The command on command line prompt would be: 'chmod +x qt-unified-linux-x64-2.0.4-online.run' I think. Success! I have now installed the latest Qt creator with Examples too. Thanks!

As a note: You created plugin to use in Designer? You will restart QtCreator after each compilation. And you will not have any debugging features while testing plugin in Designer. No, you just start another Creator and debug from there.

Can you show a header file that triggers that ? I have tested by removing the public keyword but it worked as expected and created a public section for the getter and a public slot section for the setter.

Hi, For Qt Creator plugins you should check the Qt Creator sources which are not part of Qt itself. As for Jira, it's here

Apparently related to: https://bugreports.qt.io/browse/QTCREATORBUG-17254

Hi, What kind of stuff would you like pass to lupdate and what is your purpose exactly ?

indeed macdeployqt abc.app -libpath=/usr/local/lib works. The issue was that the new option was introduced in qt 5.7.1 and I was still using 5.7.0.