Eike Ziller

Qt Creator 3.4.0 released

Published Thursday April 23rd, 2015
38 Comments on Qt Creator 3.4.0 released
Posted in Qt, QtCreator, Releases

We are happy to announce the release of Qt Creator 3.4.0 today. I’m highlighting some of the many new features below. Please take a look at our change log for a more complete list of features and fixes.

The C++ support in Qt Creator now has a new refactoring action that moves all function definitions out of a class declaration. We also added auto-completion for signals and slots in Qt 5 style connects. Just type the “&” and let auto-completion figure out the type of the object. Also new is a locator filter, All Included C/C++ Files, which finds all files that are used in your project by including them, even if they are not explicitly mentioned in your project. The filter is part of the default that is used when you just type in the Locator input field, and shares the shortcut string with Files in Any Project.

For users of the Professional or Enterprise edition we added experimental integration for Qt Test based auto tests and Qt Quick tests. It adds another navigation pane Tests, which lists the tests defined in your project, provides ways to run individual or sets of tests, and nicely shows test results in a new Test Results output pane. To try it, open Help > About Plugins (Qt Creator > About Plugins, on OS X), turn on Utilities > AutoTest, and restart Qt Creator. We also moved the Clang static analyzer integration out of experimental state. If you have at least Clang 3.6 installed, it now also supports using it with MSVC and MinGW. We also added suppression of individual diagnostics for a file, and a new page in Projects mode for managing these.

Other new features include

  • Changing the environment for running external tools
  • Searching through QML Profiler event notes
  • Using 64bit Android tool chains
  • Using generic projects for bare metal development
  • Highlighting of parenthesis in generic highlighters

See the change log for more.

You find the opensource version on the Qt download page, and Enterprise packages on the Qt Account Portal. Please post issues in our bug tracker. You also can find us on IRC on #qt-creator on irc.freenode.net, and on the Qt Creator mailing list.

Do you like this? Share it
Print this pageEmail this to someoneShare on LinkedInShare on Google+Share on FacebookTweet about this on Twitter

Posted in Qt, QtCreator, Releases


Stefan says:

CMake support is still broken…

Alergic says:

Forget it, the complete Qt Creator team is cmake-averse.

Cristian says:

I wonder if it is feasible to have a CMake generator which generates a Qt Creator Qbs project file.

At the moment Qt Creator uses the CMake CodeBlocks generator, which is a bit weird if you think about it :)

Then one could test to see how Qbs compares with Ninja!

Cristian says:

Actually it seems there is a patch which adds Qbs project support to CMake: http://www.cmake.org/gitweb?p=cmake.git;a=commit;h=f85db2f3

Stefan says:

Tried that, but didn’t work for me yet. Files in project explorer where horrible sorted and build doesn’t work at all. CMake support in Creator is still better, if it only would collect all project parts.

birdy says:

Seems to work for me

Clay Dowling says:

The entire point of cmake is that it’s really easy to build the CMakeLists.txt file yourself. Unfortunately, there’s no documentation anywhere that is accurate.

I have a skeleton project set up at https://github.com/ClayDowling/dungeonmap if you’re looking for a starting point though. Unfortunately, just because it works for me doesn’t mean it will work for you. One of the frustrations of cmake is how brittle it is.

Stefan says:

It relates to: https://bugreports.qt.io/browse/QTCREATORBUG-13695

Which was closed, but not fixed!

David Demelier says:

I wonder what you meant by broken.

I use Qt Creator since 3.2.0 combined with CMake (it’s the exclusive build system I use) and it just works.

I recall having troubles long time ago when adding include directories to a target were not applied in the editor analyzer (but compiles fine) but I have no issues currently.

In other terms, it just works :-).

Stefan says:

It does not evaluate all project parts, which results into missing includes paths in some parts of the project. Code completion will not work then on these project parts, which reduces productivity a lot.

cmake hater says:

I think CMake itself is broken. I prefer qmake in my projects.
When I tried CMake on a big project (>500M of C++ sources), the time taken for “scanning dependencies” step is absolutely unacceptable, not much less than the time of debug build. QMake on the other hand does everything quickly and the project files are smaller.

hgh says:

Debugging on Windows is broken in this release:


When can we expect a fix?

Eike Ziller Eike Ziller says:

Just to put this into perspective for people who read that comment:

This affects projects using the QBS build system with MSVC which leads to “internal” debug info instead of separate .pdb debug info. Debugging on Windows in general is not affected.

Peter says:

Can you tell us, what’s the deal with the wip/clang-oop branch?

aportale says:

It is a feature development branch which may land in Qt Creator 3.5 or 3.6. The scope is to use libclang for the clang-based code model in an out-of-process fashion (currently it is in-process).

Peter says:

Yes, all this is obvious, but what’s the reason for making it out-of-process? Is it faster or is it just for doing the slow indexing in the background?

Eike Ziller Eike Ziller says:

First of all it is guarding Qt Creator against crashes in libclang.

aportale says:

Crash-resistance and unblocking of the GUI are the immediate goals of the oop approach.
Furthermore, we are studying caching of the AST-data from multiple compile units of a project.

Christian Kandeler says:

Though I should say that I’ve never experienced any crashed with the clang code model, which I’ve been using exclusively for a couple of weeks now.

William Entriken says:

How about some screenshots?

San says:

Nice, I really like this IDE for my crossplatform developement. The biggest gripe is the debugger currently. Inspecting elements is quite cumbersome as hovering only shows the object but not the element actually used.


Shows SomeObject which has be be unfolded before we can inspect m_SomeMember which sounds like a small thing but is quite annoying when you have some deeper nesting or worse some container (e.g. vector[123].m_Member).

Code completion seems a bit off as well for some nested structures but hopefully that’s fixed when clang-oop gets integrated.

Anyways, congrats on another fine release! ^_^

jiangcaiyang says:

The same with me, hovering while debuging C++ on Windows is not that easy to use.

flashmozzg says:

So whats up with automatic (refactoring) [pure] virtual methods stubs?
It’s been in request for at least 5 years now.

Lilian Moraru says:

As an alternative you could use a library, for example “Mockitopp”.

Ray Donnelly says:

Would it be possible to make an official release of qbs to go along with this so we can build it from source?

Many thanks!

Russian_man says:

Very interesting…
Qt-ecosystem is the best thing for c++ developing. Nice work, guys!

Zing says:

Why is the project wizzard in Dark Theme still not dark: https://bugreports.qt.io/browse/QTCREATORBUG-14333

Eike Ziller Eike Ziller says:

Because theming is still considered experimental 😉

Zing says:


the simlinking hack to get the Qt kits doesn’t work on Windows any more
“As it is currently, you can only hack that by symlinking /share/qtcreator/QtProject/
(or Qt Creator.app/Contents/Resources/QtProject/ on OS X) to the same path within your standalone Qt Creator

Eike Ziller Eike Ziller says:

“Symlinks” on Windows are usually not what Unix users expect them to be, so I think you’ll just have to copy that directory over?

Zing says:

This actually used to work for me on Windows.

mklink /d QtCreator C:\Qt\Tools\… etc…

That directory is empty BTW.

exim says:

Slight off-topic, but any plans for ehancing mobile platform support for (non-QML) pure C++ Qt Widgets? Like e.g. Embarcadero does with Firemonkey (for Delphi and C++).

dirtyfreebooter says:

Thank You. QtCreator is definitely one of the best C++ editors, cross-platform, even if you are not doing Qt/UI development.

C++11 support is fairly good as well. Some issues around code completion, but steady progress.

So again, thanks. Keep up the good work. Much appreciated.

Erdi Shang says:

Thanks for the new Qt Creator!

But I found a probable issue in the Auto Test wizard:

If create a new project without “GUI Application” checked then I got “Project ERROR: Unknown module(s) in QT: console”

In Auto Test wizard files I found these code in the “src.pro”:

@if “%RequireGUI%” == “true”
QT += gui widgets
QT += console //change this to ‘core’ and worked
CONFIG -= app_bundle

TARGET = %ProjectName%

SOURCES += main.%CppSourceSuffix%

I think this may be “QT += core ” or “CONFIG += console “.

Wish to be helpful. Thanks!

Christian says:

Thanks for figuring out – will be fixed in 3.4.1.

Kind regards

Nejat says:

The auto-completion feature for Qt 5 style signals/slots is perfect. Thanks a lot. I also wished to see the “find usage” feature for old style signals/slots in different classes or sub-projects : https://bugreports.qt.io/browse/QTCREATORBUG-13929

Vitaly Bondar says:

Is qbs 1.4.0 included in this release?

Eike Ziller Eike Ziller says:


Commenting closed.

Get started today with Qt Download now