Qt Creator and other tools

Hi and welcome to devnet, Just to be sure are you using CMake or qmake for handle your project ? If CMake then this page might be of use. Hope it helps

Did you click on the link in my post above? - the answer is in there :) Here is the link in text: http://stackoverflow.com/questions/35970727/use-of-variables-like-builddir-in-qtcreator-kit-settings-in-qt5

Hi, Take a look the QAudioInput example.

Got it to work. The only way I got it to work is to launch from command line. ex: gammaray --probe PROBE_OF_CHOICE PATH_TO_QT_EXE\qt_app.exe. And of course the probe config must be the same as the app's build config. For reference, my environment is Windows 10. GammaRay on Qt 5.6 QtQuick 2.0 apps.

@Asperamanca, I grep'd through mkspecs, and this is what I have in one of my qt 5.5 installations' mkspec folder: $ grep -E -o -r 'QMAKE_PLATFORM.*?$' aix-g++/qmake.conf: QMAKE_PLATFORM = aix aix-g++-64/qmake.conf: QMAKE_PLATFORM = aix aix-xlc/qmake.conf: QMAKE_PLATFORM = aix aix-xlc-64/qmake.conf: QMAKE_PLATFORM = aix android-g++/qmake.conf: QMAKE_PLATFORM = android blackberry-armle-v7-qcc/qmake.conf: QMAKE_PLATFORM += blackberry blackberry-x86-qcc/qmake.conf: QMAKE_PLATFORM += blackberry common/ios.conf: QMAKE_PLATFORM += ios common/linux-android.conf: QMAKE_PLATFORM += android common/linux.conf: QMAKE_PLATFORM += linux common/mac.conf: QMAKE_PLATFORM += mac darwin common/macx.conf: QMAKE_PLATFORM += osx macx common/msvc-desktop.conf: QMAKE_PLATFORM = win32 common/nacl/nacl-base.conf: QMAKE_PLATFORM = nacl $$QMAKE_PLATFORM common/qcc-base-qnx.conf: QMAKE_PLATFORM += qnx common/unix.conf: QMAKE_PLATFORM += unix posix common/wince/qmake.conf: QMAKE_PLATFORM += wince win32 common/winrt_winphone/qmake.conf: QMAKE_PLATFORM = winrt win32 cygwin-g++/qmake.conf: QMAKE_PLATFORM = cygwin unix posix darwin-g++/qmake.conf: QMAKE_PLATFORM = osx macx mac darwin features/spec_post.prf: QMAKE_PLATFORM) { features/spec_post.prf: QMAKE_PLATFORM = unix features/spec_post.prf: QMAKE_PLATFORM = osx macx mac darwin unix features/spec_post.prf: QMAKE_PLATFORM = win32 features/spec_post.prf: QMAKE_PLATFORM, macx):!contains(QMAKE_PLATFORM, osx) { features/spec_post.prf: QMAKE_PLATFORM = osx $$QMAKE_PLATFORM features/spec_post.prf: QMAKE_PLATFORM freebsd-g++/qmake.conf: QMAKE_PLATFORM = freebsd bsd freebsd-g++46/qmake.conf: QMAKE_PLATFORM = freebsd bsd freebsd-icc/qmake.conf: QMAKE_PLATFORM = freebsd bsd haiku-g++/qmake.conf: QMAKE_PLATFORM = haiku hpux-acc/qmake.conf: QMAKE_PLATFORM = hpux hpux-acc-64/qmake.conf: QMAKE_PLATFORM = hpux hpux-acc-o64/qmake.conf: QMAKE_PLATFORM = hpux hpux-g++/qmake.conf: QMAKE_PLATFORM = hpux hpux-g++-64/qmake.conf: QMAKE_PLATFORM = hpux hpuxi-acc-32/qmake.conf: QMAKE_PLATFORM = hpux hpuxi-acc-64/qmake.conf: QMAKE_PLATFORM = hpux hpuxi-g++-64/qmake.conf: QMAKE_PLATFORM = hpux hurd-g++/qmake.conf: QMAKE_PLATFORM += hurd irix-cc/qmake.conf: QMAKE_PLATFORM = irix irix-cc-64/qmake.conf: QMAKE_PLATFORM = irix irix-g++/qmake.conf: QMAKE_PLATFORM = irix irix-g++-64/qmake.conf: QMAKE_PLATFORM = irix linux-cxx/qmake.conf: QMAKE_PLATFORM = linux linux-kcc/qmake.conf: QMAKE_PLATFORM = linux linux-pgcc/qmake.conf: QMAKE_PLATFORM = linux lynxos-g++/qmake.conf: QMAKE_PLATFORM = lynxos netbsd-g++/qmake.conf: QMAKE_PLATFORM = netbsd bsd openbsd-g++/qmake.conf: QMAKE_PLATFORM = openbsd bsd sco-cc/qmake.conf: QMAKE_PLATFORM = sco sco-g++/qmake.conf: QMAKE_PLATFORM = sco solaris-cc/qmake.conf: QMAKE_PLATFORM = solaris solaris-cc-64/qmake.conf: QMAKE_PLATFORM = solaris solaris-g++/qmake.conf: QMAKE_PLATFORM = solaris solaris-g++-64/qmake.conf: QMAKE_PLATFORM = solaris tru64-cxx/qmake.conf: QMAKE_PLATFORM = tru64 tru64-g++/qmake.conf: QMAKE_PLATFORM = tru64 unixware-cc/qmake.conf: QMAKE_PLATFORM = unixware unixware-g++/qmake.conf: QMAKE_PLATFORM = unixware unsupported/freebsd-clang/qmake.conf: QMAKE_PLATFORM = freebsd bsd unsupported/linux-host-g++/qmake.conf: QMAKE_PLATFORM = linux unsupported/qnx-X11-g++/qmake.conf: QMAKE_PLATFORM = qnx unsupported/vxworks-ppc-dcc/qmake.conf: QMAKE_PLATFORM = vxworks unsupported/vxworks-ppc-g++/qmake.conf: QMAKE_PLATFORM = vxworks unsupported/vxworks-simpentium-dcc/qmake.conf: QMAKE_PLATFORM = vxworks unsupported/vxworks-simpentium-g++/qmake.conf: QMAKE_PLATFORM = vxworks win32-g++/qmake.conf: QMAKE_PLATFORM = win32 mingw win32-icc/qmake.conf: QMAKE_PLATFORM = win32 winphone-arm-msvc2013/qmake.conf: QMAKE_PLATFORM = winphone $$QMAKE_PLATFORM winphone-x86-msvc2013/qmake.conf: QMAKE_PLATFORM = winphone $$QMAKE_PLATFORM

@jsulm You're right. I don't know why I didn't think of that I filled in a bug report regarding this issue here: https://bugreports.qt.io/browse/QTBUG-51728

@krzaq I'm surprised anything changed at all with the c++14 flag. Are you using 5.6.0-rc ? In my caseCONFIG += c++11 c++14 doesn't seem to do anything at all when compiling to Android. I'm using 5.6.0-rc and with CONFIG += c++11 c++14 I'm just getting -std=c++11. With Qt 5.5.1 CONFIG += c++11 c++14 I get -std=c++1y added to the mix and I can use relevant functionality (std::make_unique).

Thank you, @tekojo, for your answer.

Modifying the .pro file from the outside is not the correct idea. Since you only want to increment the build number you can mix both. VERSION from the pro file and build number generator that you can take inspiration from here

You can use this nice theme

Hi and welcome to devnet, qmake's DEPENDPATH might be of use. Hope it helps

Hi, You can set a style sheet on Qt Creator for that. Note that I don't know the impact it can have on other parts of the application. Hope it helps

Ok, here is the answer: Qt.core.incPath

Hi, The correct repository is http://code.qt.io/cgit/qt-creator/qt-creator.git/

Only a subset of QVariant types are supported by the designer plugins. Scroll down here for a list.

Check the Qt Creator instructions for snippets. I just followed the instructions and modified the auto-completed code for Q_PROPERTY so that the getter follows my company's coding style of "get" + Uppercased property name. You can probably create a snippet for what you want.

QDockWidget and QMainWindow are tied. That doesn't prevent you to use another QMainWindow as a central widget for your QMainWindow even though that would be a bit strange. Note that if you only want to work with dock widgets nothing forbids you to not use any central widget.