Lars Knoll

Qt 5.0 RC2 released

Published Thursday December 13th, 2012
83 Comments on Qt 5.0 RC2 released
Posted in Uncategorized

It’s been one week since we released the first Release Candidate for Qt 5.0 during the Qt Developer Days in Santa Clara. After evaluating the feedback and going through the list of reported bugs, we decided that RC1 wasn’t good enough for a final release.

We have been using the last week to fix a lot of the reported bugs, and are now happy to announce that we have a second release candidate available for testing. You can download it from It is also available from the Digia customer portal for commercial licensees.

This release candidate looks a lot better then RC1. There are very few known issues with it and almost all P0 and P1 bugs got fixed. A lot of additional work has happened in fixing documentation, polishing the examples and making the whole installation experience smoother.

Once again, I’d like to invite as many people as possible to give the RC2 a try and report back any issues that you find. If everything goes well, we will hopefully be able to release Qt 5.0.0 final next week!

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

Posted in Uncategorized


Robin Lobel says:

Great !
What will be the precompiled targets for Windows ? (MinGW 32/64, MSVC2010 32/64, MSVC2012 32/64, …)

Robin Lobel says:

I mean, for the final release

Shiyu Tang says:

I have tried to build Qt5 beta2 with MinGW, and the build process is OK. But there is a problem with WebKit that makes crash.

Tuukka Turunen Tuukka Turunen says:

@Robin Lobel: We are working to include also MinGW as well as VS2012 installers, but will not block 5.0.0 release if these are missing, in which case these will arrive with 5.0.1.

Christoph Cullmann says:

A MSVC 2010/12 64bit compiled version would be a nice addition, IMHO.

Robin Lobel says:

Thanks ! I’m really crossing my fingers for MinGW64+VS2010 x64 builds (x86 is less and less relevant)

Fabio says:

Ok, but please, if the first release will not contain mingw binaries, at least check and fix problem (if any) in Qt5 sources compilation so we can build ourself with mingw.

Rathias says:


Malek Khlif says:

Good Work :))) Qt isThe BEST 😉

smoggy says:

Sooooo fast !

Please fix the height/width:childrenRect.width/height loop warning.

has this been reported, is there a task in our bug tracker? If not, please report it 🙂

Evan says:

Wow! I can’t wait until the final release! I’m sort of at a waiting game currently because I am going to be writing a large project with Qt, and I may as well use Qt 5 if it gets out in time. The OpenGL integration is perfect as well. Now to just wait until Digia can bring iOS and Android builds into the tool-chain as Nokia did with Symbian. Oh, and don’t focus too much on QML. It’s great for UI designs but I know a lot of Qt developers who still want the C++ side of things improved upon regularly.

Keep up the great work!

Fabio says:

Me, for example: I prefer C++!

Sebastian says:

I’m totally agree with you Evan.
Have a great coding…

Danny says:

I downloaded this today. So far I’m impressed by the cleaned up distribution, the C++11 connect and the elimination of much of the old junk from Qt3.

But what happened to the unified toolbar for C++ Qt/Mac applications?! This feature is now described as ‘obsolete’ in QMainWindow and as a result OSX apps with toolbars look like *crap*.

Is this another tactic to force Mac developers to adopt QML (which does support modern toolbars)?

Will Stokes says:

Yikes, I’m only just noticing this now as well. There is a QtMacUnifiedToolbar class floating around but it only allows adding actions. Since I have custom widgets in my toolbar this is a show stopper for me. Hopefully this can be addressed. Until then I guess I’ll have to stick with Qt4.8.*.

Jens says:

Danny, Will: Don’t worry. We are fully aware of the lacking unified toolbar.
As Will mentions, you can use QtMacUnifiedToolbar with 5.0 and it gives you an even more native toolbar than the one you had in 4.x. We already had a patch to merge it into 5.0 but since we were not entirely sure if the API was perfect yet, we decided it was a good idea to postpone it until 5.1. (see,38144) This way we can also ensure it will be usable from QML as well.

danny says:

Thanks for the clarifications. The old implementation was a hack to be sure but it was usable.

Will the replacement version in 5.1 work in the Designer?

Will Stokes says:

@Jens: thanks for the reply, but are their plans to add a

QAction* QtMacUnifiedToolbar::addWidget(QWidget* w);

method to QtMacUnifiedToolbar? Unless that is added I see no way to accomplish the following in Qt5.

Samuel says:

That has nothing to do with QML (which I don’t really think addresses this specific issue), and everything to do with the rewrite of core parts of QtGui to use QPA (Qt Platform Abstraction) for great code simplification and increased maintainability going forward. However, since QtGui / QtWidgets are now fully platform independent, the platform dependent part being implemented as plugins, platform specific APIs no longer make sense. The decision of windowing system is no longer made at compile time but at run time.

The plan is to instead have platform specific functionality in separate modules. Down the line this should allow even heavier customization for a given platform, and adding APIs that would have no meaning on other platforms. QtMacExtras is currently under development at You might be interested in this:

danny says:

That looks really good but I have a few queries:

1) The MacUnifiedToolBar property didn’t just make the toolbar look OSX-like, it also styled the rest of the window, including the status bar. Are there planes for a dedicated statusbar class to reproduce the Qt4 behavior?

2) Will there be QtDesigner integration? I still use the designer heavily.

3) Will the new toolbar support the features expected of a Cocoa NSToolBar such as the customization menu, icon and text modes etc?

Oliver Knoll says:

@danny: 3) From what I understand the “new” QtMacUnifiedToolbar (which currently is more of a “working title”, until fully integrated into the official “Qt 5 API” (as a platform dependent plugin, as mentioned previously) does not just “look like” a native toolbar, but under the hood really /is/ an NSToolBar. With all the drawbacks (“not so easy/possible to integrate custom QWidgets, since NSToolBar does not allow that either”) and advantages (“since it actually is an NSToolBar, you can do everything with it that you can also to with Cocoa and an NSToolBar”).

Fabio says:

Oh no!!!
Must suspect that the user “TheTrueDigia” always tell us the truth? 🙁

Awesome! I don’t know what I use to develop apps for Ubuntu(Linux) Qt is a life saver… hope Pyside gets better Gui binding in the final release. 🙂

David Johnson says:

The documentation build (and build instructions) need to be fixed. I’m trying to build docs, but it keeps choking on missing Makefiles.

David Johnson says:

Makefiles were not missing, just had root permission somehow. I chowned the entire build tree, and have now successfully build the docs.

Danny says:

I hit QTBUG-28097 (‘initializer_list’ file not found) when I tried to use the Clang C++11 features (lambdas) in OSX 10.8. I found a workaround but I’m astonished that this issue (first discussed in June ’12 on the interest list) has yet to be addressed as of RC2.

Mosi says:

How about embedding a qml into QWdiget? Did it fixed?

dado says:

What about the VS2012 Qt add-in?

Tuukka Turunen Tuukka Turunen says:

@dado: It is on the works. We aim to release VS Add-In 1.2.0 together with Qt 5.0.0 or a few days after. It includes VS2012 support and a few other improvements. There is a RC of it available at if you want to give it a spin. That one is missing most of the docs, but otherwise functionality should be there.

Gateslu says:

what a good news!

Chris says:

Could you please clarify the ANGLE vs OpenGL on Windows? Well, I understand that QML/GUI stuff will use ANGLE but does it mean that the QGLWidget will use ANGLE too? What if one wants to use OpenGL 4.3 stuff?

Does this apply to MinGW? Will there be a precompiled MinGW distribution too?

Samuel says:

Desktop OpenGL won’t be useable with an ANGLE build of Qt unfortunately. It is still possible to build Qt with desktop OpenGL support for Windows, but it’s a compile time decision and for the released packages ANGLE has been chosen. I have some hope that we could make the choice be a run-time decision instead, maybe in Qt 5.1, but it remains to be seen how feasible that would be.

Chris says:

That would be nice to have. Thanks!

Sean Harmer says:

If you have non-broken OpenGL drivers then compile Qt yourself using configure.bat -opengl desktop to avoid the use of ANGLE. Qt will then use the native OpenGL drivers and you will have access to even OpenGL 4.3 Core profile if your driver and hardware supports it.

Chris says:

Thanks! Fortunately, what I need is just OpenGL 2.0 ES anyway (for now). I just wonder how ANGLE compares to real OpenGL 4.x and OpenGL ES 2.0 (in performance, stability and compatibility).

Chris says:

BTW. What drivers I have (AMD) doesn’t matter. The drivers that the end users have is what really matters 🙂

Zeke Connor says:

Is there any plans for Digia to get dbus to run on Windows? I mean adding it 3rd party like you do webkit, etc.? It would be nice if I could create applications to communicate with each other.

Evan says:

I believe you can do that already using native win32 code. Just play around with the messages and see if you could intercept it in a Qt application. To do it you would have to link against a native Windows DLL and invoke a WndProc listener. If you were clever enough you could probably even use signal and slots. When you catch the message just use emit to fire a signal and connect it to a slot like opening a message box with the message from your application. In theory, you could utilize this to replicate a lot of D-Bus’s features.

Richard says:

How about QLocalServer w/ QLocalSocket?

Gives you socket-like connections between processes that you can use in a very similar way to TCP streams.

On Windows this uses “Named Pipes” so you can talk to 3rd party applications this way – which would obviously not be possible using a Windows port of the dbus service.

Danny says:

Take a look at boost process for a cross-platform interprocess library. Windows is too different from ‘nix to make a port of dbus practical.

toby says:

good job

not long to the end, good work, congratulations!

Anton says:

VS2008 would be nice too,
or at least include a vs2008 solution which enable us to compile it ourself.


Anton says:

I just installed it on my kubuntu 10.12 64 bit.

1. I created a qt-qui project
2. I tried to copile it and got the error:
:-1: Error:cannot find -lGL
:-1: Error:collect2: error: ld returned 1 exit status

Is there a doc telling me what dependencies I need

Anton says:

OK I found it, i only didnt find an INSTALL.TXT somewhere

Anton says:

Another problem:

Just try to create a html5 project:
qtcreator tells me that there is no valid “Kit” for that….
so I have to look again ….

Chris W says:

You need to tell Qt Creator, which is what is complaining, about the relevant bits of Qt5 and put them together in a Kit. This is a problem outside Qt5.

Anton says:

Is there an howto what to write in a kit?

I added some kits (trial and error) but since I do not find
a real info in the docs … I stopped wasting time.

Is html5 for mobild devices only? (I try a desktop application)

QtCreator is for QT and it has an option to create a html5 project which
(for me ) does not work.

So I would prefer that you drop completely this feature,
or that to add the necessers documentation/howto telling
what I need to do.

Thanlks and a happy new year.


Ying Yin says:

Great work!
And I am using QWindow (QBackingstore) now for rendering to backingstore in a sub-thread timely and not in paintEvent.
It most works, but some QT events are not correctly handled and crashes.
So, I have a question that: What is the aim of exposing QWindow & QBackingstore, can they be used in a separated thread other than main UI thread?

Maissiou2 says:

Thanks! very great news!

I had a problem with error: Compiler not found. But I just got it to work after downloading/installing MSVS 2010 Express. I had to go to option->Build&Run->Compiler and set/add one of the compilers manually. I hope the final Qt 5.0 version will come with a pre-packaged compiler.

Maissiou2 says:

Some OpenGL examples are not working in Windows. There is also missing library files such as : ‘demo_shared.lib’ (error: LNK1104) when running Path Stroking example for example. I just did a fresh Qt 5.0 rc2/Windows installation and many examples, especially some OpenGL examples, are not working because of missing paths/links/libraries. I am a new user … perhaps could someone let me know If I am missing something?

Andre' says:

That’s a known issue, and actually already fixed in the ‘dev’ branch, see So far the plan was to not have that fix for 5.0. You can build the project and the library by opening the .pro file in the parent directory.

Kit Ham says:

Looking much neater!
Unfortunately, I’m still experiencing QTBUG-28483. The QML multi touch stuff is having issues on my Trackpad in recent releases. I feel this is quite a critical bug.

Qt4iOS says:

Looking forward to the final release! Can confirm that this version is compatible with Apple iOS (4.0+). Unfortunately there are 2 files that need to be patched from “out-of-the-box” Qt5.0 before it will build for iOS (which won’t be an officially supported platform until at least Qt5.1).

The Qt4iOS platform plugin from Qt4.8 has been ported to Qt5.0, and should be available for evaluation once Qt5.0 is released.

At this time, it is not possible to use QML2 on iOS due to technical issues which prevent V8 from running on iOS.

Qt4iOS says:

*It’s not possible to use QML2 on non-jailbroken iOS. Qt5.0.0RC2’s QML2 & SG are working on iOS (now that the initial port of V8 to iOS is complete).

terry says:

Do you have any plans to make QtOpenCL as a module of Qt?

Lauri W Ahonen says:

Will we be getting pdb files this time? Please?

Daniel Minan says:

When the SDK (commercial and GPL versions) will be released?

Tuukka Turunen Tuukka Turunen says:

@Daniel Minan: Qt 5.0 already comes as an offline SDK containing Qt Creator, Qt libraries and tools. We will change this to be an online SDK in early 2013, maybe in February, depends a bit how things go.

7 says:

Where is that offline SDK? All I see on download links are the barebone libraries.

Fabio says:

I think Tuukka mean the library download itself.

Daniel Minan says:


In there isn’t any offline SDK (only link for old Nokia SDK). How can I install libraries, qt creator and tools and “make” the sdk with qt 5.0 RC2?

Robin Lobel says:

Daniel: the 4 links to “Qt libraries 5.0 RC 2” actually are the SDK (lib+qt creator)

Sergio Migueis says:

Why the webview component doesn’t work????

Oliver Knoll says:

Maybe there’s a bug? 😉

HZ says:

I’m not sure if it’s a bug or by design, but here is the problem.

The QML Text doesn’t show Chinese characters if font family is not set.
Please try this snippet with qmlscene:

import QtQuick 2.0
Rectangle {
Text {

If the font family has to be set for it show a specific language, then how can we conveniently switch languages in the UI?


HZ says:

A web browser (use 好), notepad.exe, etc. will show the Chinese character without the need to set the font. They kind of automatically find the right glyphs and show the character. Can’t QML Text do that for the user?

Fabio says:

The problem with the -L compiler’s option is still there:

Under windows, for some projects, each -L option
is added two time, one of which without “” so when paths are containing spaces
te result is as the following:

g++ -c -pipe -fno-keep-inline-dllexport -O2 -Wall -Wextr
g++ -Wl,-s -Wl,-subsystem,console -o ..\..\..\bin\moc.ex
g++: error: Files\Microsoft: No such file or directory
g++: error: Platform: No such file or directory
g++: error: SDK\Lib\.: No such file or directory
g++: error: Files\Microsoft: No such file or directory
g++: error: DirectX: No such file or directory
g++: error: SDK: No such file or directory
g++: error: (June: No such file or directory
g++: error: 2010)\Lib\x86: No such file or directory
mingw32-make[5]: *** [..\..\..\bin\moc.exe] Error 1

Fabio says:

Al the project involved are some of those under:

Fabio says:

And with Qt-4.8.4 the “paths with space hell” is also present (default MS SDK installation paths)

g++ -c -include tmp\obj\release_shared\qt_gui_pch.h -pipe -fno-keep-inline-dllexport -O2 -Wall -Wextra -frtti -fexceptions -mthreads -DQT_SHARED -DQT_THREAD_SUPPORT -DUNICODE -DQT_LARGEFILE_SUPPORT -DQT_BUILD_GUI_LIB -DQT_NO_USING_NAMESPACE -DQT_MAKEDLL -DQT_NO_CAST_TO_ASCII -DQT_ASCII_CAST_WARNINGS -DQT3_SUPPORT -DQT_MOC_COMPAT -DQT_USE_QSTRINGBUILDER -D_USE_MATH_DEFINES -DQT_NO_DIRECTDRAW -DQT_USE_BUNDLED_LIBPNG -DPNG_NO_ASSEMBLER_CODE -DQT_NO_CUPS -DQT_NO_LPR -DQT_NO_OPENTYPE -DQT_NO_STYLE_MAC -DQT_NO_STYLE_GTK -DQT_NO_EGL -DQ_INTERNAL_QAPP_SRC -DQT_NO_DIRECTWRITE -DQT_DLL -DQT_NO_DEBUG -DQT_CORE_LIB -DQT_HAVE_MMX -DQT_HAVE_SSE -DQT_HAVE_MMXEXT -DQT_HAVE_SSE2 -I”..\..\include\QtCore” -I”..\..\include” -I”..\..\include\QtGui” -I”tmp\rcc\debug_shared” -I”tmp” -I”..\3rdparty\wintab” -I”image” -I”..\3rdparty\libpng” -I”..\3rdparty\zlib” -I”..\3rdparty\zlib” -I”..\3rdparty\harfbuzz\src” -I”dialogs” -I”..\..\include\ActiveQt” -I”tmp\moc\release_shared” -I”.” -I”c:\Qt\mingw32-qtproject\include” -I”c:\Program Files\Microsoft DirectX SDK (June 2010)\Include” -I”c:\Qt\OpenSSL-Win32\include” -I”c:\Qt\icu\include” -I”..\..\mkspecs\win32-g++-4.6″ -o tmp\obj\release_shared\qfontengine_win.o text\qfontengine_win.cpp
mingw32-make[2]: *** No rule to make target `June 2010)/Include/dcommon.h)’, needed by `tmp/obj/release_shared/qrawfont_win.o’. Stop.
mingw32-make[2]: Leaving directory `C:/Qt/qt-everywhere-opensource-src-4.8.4/src/gui’
mingw32-make[1]: *** [release-all] Error 2
mingw32-make[1]: Leaving directory `C:/Qt/qt-everywhere-opensource-src-4.8.4/src/gui’
mingw32-make: *** [sub-gui-make_default-ordered] Error 2

Albert says:

Trying again! 🙂

Why did you left the 4.8 kinf of deployment solution (I mean, separate downloads for Qt libraries and Qt Creator)? Is there a special reason for that? I think that the previous solution is a little more versatile, as it allows to update Qt Creator indipendently in an easier way.

Also, I loved the precompiled demo that came with Qt 4.8, will it return? 🙂

Tuukka Turunen Tuukka Turunen says:

@Albert: The reason to bundle is desire to have a more integrated package with Qt and tools. In 5.0.0 it is offline, but created with online capable framework. So we hope to be soon (during Q1/13) change it to be online, after which it is easy to update separate components. The demo launcher was dropped in favor of having the demos and examples prominently in Creator and encouraging users to build these themselves (thus lowering the barrier to try modifications and learn Qt). Demo launcher could make a comeback, but now focus is in the Creator based approach.

Dr. Sykero says:

I’m trying to compile one of the QtQuick examples, but I get an error: GL/gl.h: No such file or directory. Do I need to install OpenGL libraries or should they be included in Qt5? It would be nice if it worked out-of-the-box. 🙂

Robin Lobel says:

Some GL examples in RC2 are still broken, that should be fixed for the final release I guess.

Dr. Sykero says:

Well, the same error occurs when creating a new QtQuick2 application. 🙁

Raynerd says:

Wow so fast 2nd RC, I can’t wait no longer for Final Release, when I meet Qt five years ago it was first sight love 🙂 nowadays more cubans share my afinity for the best framework ever exist. BTW, I hope some day have full access to internet for contribute by coding for this amazing framework.

Commenting closed.

Get started today with Qt Download now