Eike Ziller

Qt Creator 3.1.0 released

Published Tuesday April 15th, 2014
Posted in Qt, QtCreator, Releases

We are happy to announce the release of Qt Creator 3.1.0! This release of Qt Creator is packed with bug fixes and improvements, not to forget some new experimental features.

We finally integrated a Clang-based C/C++ code model as an option for code completion and semantic highlighting. It is experimental so far, so you need to enable the plugin in Help > About Plugins > C++ > ClangCodeModel, restart Qt Creator, and tell it to actually use it in Options > C++ > Code Model. We are interested in your feedback on how well it works. Please report issues on our bug tracker or get in contact with us on the mailing list or irc.

iOS support has moved out of experimental state, and fully supports QML debugging and profiling now. Also, several issues with debugging have been fixed, and many little things were tweaked (for example, you can now set the simulated device in the simulator run configuration).

In exchange we added a new experimental plugin for another platform: WinRT. You can read more about it in its own blog post here.

An important note is, that we drop support for debugging with versions of GDB that do not have a Python interface. This includes the version of GDB that is shipped with older versions of Xcode on Mac OS X. The good news there is, that we put a lot of effort into making debugging with LLDB a great experience in Qt Creator, so you should just use LLDB instead :)

Also notable is the experimental Beautifier plugin, which allows you to apply different external source code formatters on your files. It currently has support for Artistic Style, Clang-format and Uncrustify. Many thanks to Lorenz Haas for contributing this!

Additionally, Android support has received many tweaks again, including some minimal support for editing Java files with highlighting, indentation and keyword completion. You can now manage debug tokens and runtime configurations for QNX from Qt Creator, and debugging on QNX now supports more pretty printers as well. The QML Profiler and Qt Quick Designer have received many fixes, the Qt Quick Application templates have been simplified, support for qrc has been polished (for example, qrc files now appear as nodes in the project tree), and much much more. You find a more thorough overview in our change log.

Qt Creator 3.1.0 is part of the Qt Enterprise Embedded update today, and it will appear as an update in your Qt online installer (this may take a bit while it is rolled out to the mirrors). The Qt Creator open source standalone packages are also available on the Qt Project download page, and Enterprise Customers find them in the Qt Account Portal.

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


Alan says:

I currently have Qt 5.2.1 installed on my Mac, i.e. I also have Qt Creator 3.0.1 installed (and my CMake-based project works fine with both).

Now, with Qt Creator 3.1 being out, I thought I would give it a try. I therefore downloaded it and decided to (physically) replace my copy of Qt Creator 3.0.1 with that of Qt Creator 3.1. What a bad move!

I naively thought that it would all be fine, and maybe it will be for most people, but clearly not for me. I tried to open my CMake-based project, but I am being told that no kits are suitable for CMake projects, and to click on the Configure button confirms that no kits or Qt versions have been auto-detected. Anyway, it’s getting late on this side of the world, so I will have to look into it tomorrow, but… not happy!

Eike Ziller Eike Ziller says:

The “auto-detected” kits are written into a config file for Qt Creator by the installer. That is located in Qt Creator ‘s app bundle. By replacing your Qt Creator 3.0, you also removed this information. If you still have the old Qt Creator app in your trash, you can copy Qt Creator.app/Contents/Resources/QtProject into the new Qt Creator. Otherwise: http://qt-project.org/doc/qtcreator-3.1/creator-targets.html

Alan says:

Hi Eike,

The OS X replace feature really replaced Qt Creator 3.0.1, so it never ended up in my Trash.

Anyway, wouldn’t it be better to have that config file created by Qt Creator (if and whenever necessary) rather than its installer? This would certainly avoid the problem I am facing.

Regarding the link you gave, I actually first needed to add a Qt version (http://qt-project.org/doc/qtcreator-3.1/creator-project-qmake.html). From there, I was indeed able to add a Kit. So, yes, I am now back on track. (Thanks for the reply and ‘sorry’ for the rant — it’s just that it’s never nice when things break when they really shouldn’t be… :))

Alan says:

By the way… thanks a lot guys for this new release of Qt Creator! :)

Francesco says:

I’ve got the same problem in Windows.

I have Qt 5.2.1 installed, with the problem of the “incompatible devices” for android.

I installed Qt Creator 3.1 and it recognized only the kits for BB10… I had to manually add Qt 5.2.1 and then the kits.

Is it possible to copy the “kits” file from old Creator ? Do you know the file name ?


TheBootroo says:

I love the new Clang Code Model, but there are some issues with coloration :

– types and varnames aren’t colored inside the ‘foreach ()’ brackets

– in header files, the whole line ‘class XXXX : public YYYY’ has the same color

– in header files, in member declaration, nothing is colored excepted keywords (types and names aren’t)

That’s all I see at the moment…

And maybe a slight delay for coloration (like 500ms).

TheBootroo says:

Here is a small comparaison between Built-in and Clang code models in QtCreator 3.1 for header files :


Source files are pretty well handled, but headers is just plain regression to me.

Eike Ziller Eike Ziller says:

what you see is the non-semantic highlighting, which means that the clang highlighting doesn’t run at all, or fails to parse anything, in your case
can you please create a report at https://bugreports.qt-project.org/browse/QTCREATORBUG . that’s much more suited for tracking issues

Marcus says:

I wonder if you’re having a case of the code model bug that I’ve seen;


My work-around is to use the “QT Creator Built-in” completion for headers, and Clang for everything else; sort of OK.


Flavio says:

Trying the code beautifier plugin. Built astyle on my Mac. It works from the terminal. Qt Creator gives “Error in Beautifier: Cannot create temporary file “”: Cannot create temporary file in /: Permission denied.”

andre says:

Please put bug reports or feature requests on bugreports.qt-project.com. The infrastructure there is much better suited to handle such issues.

Adi says:

Hi guys, first of all thanks for the effort you’re putting for building a very solid IDE. In order to make this product better, I am providing you a feedback as a daily user of this tool.

Ability to browse through AOSP code, especially the native part *including* the Linux kernel, is the main purpose I use Qt Creator for. Eclipse just doesn’t scale too well in this task, but I’m afraid that Qt Creator doesn’t do it too well either. I am talking here about the latest release of Qt Creator (3.1.0) running on a 64-bit Ubuntu machine.

I cannot say that I’ve expected blazing speed of parsing the project this size (nearly 10GB). But again, I would not expect that it would be stuck at 20% after you let it running almost for 24h! Both physical and swap memory has been also eaten up almost completely: 7GB + 4GB!

Machine is Intel i5 quad-core 2.5Ghz with 8GB of RAM and 4GB of swap partition.

Could you please comment on this?



andre says:

@Adi: The code model representing is held in memory. There’s no 1:1 relationship between source code size and code model size, but if you truly have a “10 GB” project it’s unlikely to fit into 8 GB RAM. Since your code is static anyway, using a tool made for _code browsing_ like http://woboq.com/codebrowser.html might be a better solution.

Commenting closed.

Get started today with Qt Download now