Eike Ziller

Qt Creator 4.7 RC released

Published Thursday July 5th, 2018
18 Comments on Qt Creator 4.7 RC released
Posted in Dev Loop, Qt, QtCreator, Releases

We are happy to announce the release of Qt Creator 4.7 RC!

After 2 weeks and 70 changes since the Beta2, we think that we are almost ready for the final release of Qt Creator 4.7. So this is a good time to give us some last feedback, best done through our bug tracker.

Get Qt Creator 4.7 RC

The opensource version is available on the Qt download page, and you find commercially licensed packages on the Qt Account Portal. Qt Creator 4.7 RC is also available under Preview > Qt Creator 4.7.0-rc1 in the online installer. Please post issues in our bug tracker. You can also find us on IRC on #qt-creator on chat.freenode.net, and on the Qt Creator mailing list.

Do you like this? Share it
Share on LinkedInGoogle+Share on FacebookTweet about this on Twitter

Posted in Dev Loop, Qt, QtCreator, Releases


Vladyslav Stelmakhovskyi says:

crashing all the time

jason says:

Vlad, I assume you’re developer, so how do you expect them to identify and fix the issue with that kind of report?
1. When did i crash, on what platform?
2. What about the crash information?

Vladyslav Stelmakhovskyi says:

If I would create a report, I’ll do it in Qt’s bugtracker
basically, issue is solved deleting .config/QtProject folder

Eike Ziller Eike Ziller says:

Probably https://bugreports.qt.io/browse/QTCREATORBUG-20741 🙁
Fix should be available in tomorrow’s nightly snapshot (http://download.qt.io/snapshots/qtcreator/4.7/4.7.0/)

Vladyslav Stelmakhovskyi says:


Vladyslav Stelmakhovskyi says:

now its fixed, thanks again

jason says:

QML Enums still not syntax highlighted.

Louis says:

Could indeed be great to have it in this version as the next final release is planed for ~Nov 20 2018, according to https://wiki.qt.io/Qt_Creator_Releases, and because QML Enums are already shipped in Qt 5.11 🙂

Thanks for your hard work!

jason says:

QML Enums shipped in 5.10… Last November if memory serves…

Prav Ogrev says:

It is quite strange that instead of letting Clang code model deliver more info to existing code model as soon as info is ready it is done like “one OR another”. Like as soon as you get AST from clang you go throught it and add details which current code model was not sure about. In this case you would get speed of build-in code model and adopting clang code model would not be so hard for developers.
From user’s point of view something seems done better in old code model (almost never crashes and is MUCH faster) … something is better in new Clang code model (auto types, more warnings).
At least there from user’s point of view there is a need to quickly move from one code model to another. Why not to allow both code model to be build and ready to be used (I expect that both code models have similar “inteface”)? God knows how long will it take for clang code model to be as robust and fast as build-in code model (if ever … currently small projects need to wait about 30 sec for clang code model)

YH says:

Curiously, code model in this version fails to parse a file that worked OK with beta2. This is not new though – persistent issue with Boost that comes and goes :-). I’ll wait for 4.7 and maybe try filing a bug.

if.hpp:131:1: error: pasting formed ‘BOOST_PP_TUPLE_ELEM_O_3(‘, an invalid preprocessing token

jason says:

I realize I complain a lot, but there’s a lot to like in this update. I am very grateful to whomever enabled the modern cast fixit for the cast warning!!

Dmytro says:

Would be great to have an option for project view mirroring files tree without displaying build targets, we have a lot of “technical” intermediate targets and generated files, the project tree view looks very messy, much less usable comparing to the old QtCreator version. As a workaround for a while I kept using the old version of cmake to force QtCreator to fallback to the old project view but it stopped working at some stage.

Eike Ziller Eike Ziller says:

You can use the “File System” view for a completely file system tree centric view on your project directory.

Jon Harper says:

Will there be proper C++17 support (CONFIG += C++17), or does that have to wait for a QMake update in (hopefully) 5.12?

Jon Harper says:

Ah, I see now that “CONFIG += c++1z” works but there is a lack of interest in aliasing “c++17” to “c++1z”, which makes little sense to me. There are a slew of questions on Stack Overflow and elsewhere asking how to enable C++ 17 support.

Konstantin Isakov says:

So far so good, can’t wait for the release! My main wish right now is that all symbols are followed using Clang model. Hope you’ll get there soon, fingers crossed here 🙂

Karim Benyamna says:


Thanks for this version especially after the nightly build that solved the crashes.
But I have hard time running the full clazy + tidy on huge project, it seem’s spammed by qt and gcc header files (freeze then crash after dozen of hundreds of messages), the typical clang key to ignore system headers doesn’t seem’s to work.
Am’I missing a way to configure it ? When can I found a tutorial about the possible configurations, especially using qt creator if possible, as it seem’s to accept only some specific options.
The final gcc command in the makefile used for building is quite huge (~20 k symbols) and I don’t think clang model reuse it somehow.

Keep up the good work!

Leave a Reply

Your email address will not be published.

Get started today with Qt Download now