Qt 4.8.3 Released

Published Thursday September 13th, 2012
46 Comments on Qt 4.8.3 Released
Posted in migrate, Qt

Today’s blogger and presenter of Qt 4.8.3 is Tuukka Turunen, Director Qt R&D at Digia.

Most of the activities have lately been around Qt 5, but rest assured – Qt 4.8 is still very much alive as well! I am extremely pleased to announce that we have released 4.8.3 today together with the Qt Project. Since the previous release there are over 200 fixes and improvements included to the 4.8.3 making it worthwhile to migrate into for most 4.8 users.

Highlights of 4.8.3 include changes to better support Mac OS X 10.8 and QNX, as well as new WebKit (2.2.3). With over 200 improvements there are many really important ones to talk about, but for now lets just say that there are a lot of other improvements, for example to QtCore, QtGui and QtNetwork modules.

A detailed list of the fixes and improvements, as well as a change log showing differences from Qt 4.8.2 can be found here.

As agreed with the Qt Project, Digia has packaged and tested Qt 4.8.3, which feeds from the Qt Project 4.8 branch. We will keep providing patch releases to 4.8 as long as needed. Currently we believe that at least two more patch releases will be needed. Qt 5 provides high compatibility with Qt 4 and we recommend Qt users to migrate their active projects to Qt 5.0 after the final version release is available.

We have tagged the Qt 4.8.3 release in the Qt Project repository. The source packages and stand-alone installers for Qt 4.8.3 are available for download at http://qt-project.org/downloads. For commercial licensees there is also online SDK update available. For more details, please see qt.digia.com.

We look forward to your feedback and hope you use the Qt Project mailing lists to keep the conversation going.

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

Posted in migrate, Qt


Unfortunately link to change list is broken ;-(

“We’re sorry, but that page doesn’t exist…”

Lars Knoll says:

@Ludek Fixed now, thanks for noting.

Uku says:

As new vs is just released we expect that support for it is also coming soon?

Robin says:

Sooo why cant i decide where to put it on the mac? i only get to choose the hard drive and not a location in the hard drive and when the installation is done i can’t find it…

Alan says:

So… there is an SDK update, but only for commercial users? So much for telling us, non-commercial users, that we should be using the SDK. Seriously, whatever you decide for Qt 5, please make sure that (some of) your users are not left unable to upgrade! This is becoming extremely frustrating to see new updates for Qt and Qt Creator, and not be able to upgrade!

Steph says:

Thank Digia for getting 4.8.3 available on QtProject.

Alan, the SDK is the Nokia SDK you use to build on Symbian or Meego smartphones. As they get rid of Qt, this won’t be updraded anymore I think. If you don’t care about nokia targets, just un install it, and install qt creator and qt 4.8.3 side by side.

Digia has his own SDK for commercial users, but QtProject still don’t have one, and I don’t know if it is in schedule to have an SDK for QtProject as well.

Steve says:

@Alan @Steph

No, the SDK is Qt SDK not Nokia SDK. So if someone is changed and Qt SDK is dead, why some Qt/Digia man post an article where tell to community the end of Qt SDK. So we start download separatly creator and libraries.
But someone have the ‘balls’ to clarify this situation!

Alan says:

The primary reason for me to use the Qt SDK is that on Linux, you don’t have to build everything from source. I used to do that and having three different Linux machines, the whole process used to be very time consuming. Now with the Qt SDK, I just need to install and that’s it. I have just had a look at the Qt 4.8.3 downloads and it would seem that, on Linux, you still need to build everything from source or am I mistaken?…

@Alan: the simple reason is that we have not had enough manpower to create an SDK for the past few months. The process to create an SDK is quite complex, especially when it still involved figuring compatibility with the Nokia platforms.

But rest assured that an SDK is in the plans for future releases. Depending, of course, on having manpower available to create them and test the installers.

NoName says:

@Thiago: Thanks for the clarification

Gábor Horváth says:

Isn’t it possible to “just” strip down the commercial SDK, so it require less initial effort?

Gábor Horváth says:

Never mind.. just realized the codebase is also different. That is unfortunate.

Alan says:

Thanks Thiago. Let’s just hope there will be enough manpower…

portoist says:

Thanks a lot! Is there a changelog anywhere?

7 says:

portoist – try reading the post and you will realize the changelog is there 😉

As commented the SDK many are referring is Nokia Qt SDK created for the purpose of Symbian and MeeGo application development. Qt Project SDK is planned with main focus in 5.0. And, as also already commented, by just installing 4.8.3 and Creator separately you get quite close to the basic SDK.

Eric says:

is the new QTWebKit if included in an app has any chance to be accepted for the Apple Store?

fonzi337 says:

Qt Commercial’s blog mentions that support for VxWorks has been added (http://www.digia.com/en/Blogs/Qt-blog/Tuukka-Turunen/Dates/2012/9/qt-commercial-483-with-vxworks-support/), but I don’t see it mentioned in this Qt blog post. Does this mean that the VxWorks support has not been contributed to open-source Qt and is only available with a commercial Qt license?

@fonzi337: Yes, but it is not black/white. VxWorks as an operating system is not available under open-source license, so having a complete Qt support available does not matter. Naturally we are contributing all the general improvements to Qt, as well as actually many of the other modifications. At the moment there also exists certain code that is not possible to be available under LGPL. That is not our call. In the software industry there exists many licenses that are incompatible with LGPL, so not everything can ever be contributed. We believe that it is in everyone’s best interest to keep Qt thriving and getting better every day. But we have to respect also those areas of the SW industry that are not open-source.

Peter says:

Win7 + Qt4.8.3 (mingw) + QtCreator 2.5.2 – Build error when add *.pro to project

process_begin: CreateProcess(NULL, binrcc.exe -name test ..testtest.qrc -o releaseqrc_test.cpp, …) failed.
make (e=2):
mingw32-make[1]: *** [release/qrc_test.cpp] Error 2
mingw32-make: *** [release] Error 2
13:02:41: The process “C:Qt2010.04mingwbinmingw32-make.exe” exited with code 2.
Error while building/deploying project test (target: Desktop)
When executing step ‘Make’

Luca says:

So, just to clarify a bit, since here we are still under the Nokia umbrella, is there any chance that we, as symbian/meego developers, would seen anytime soon an update to the QtSDK in order to have Qt 4.8 support, Updated QtCreator and so on?

Danny says:

Still no support for the LGPL SDK? Rubbish.

The standalone mac installers are useless if you need to maintain side-by-side installations (unless someone has updated them).

Should I just delete the SDK all together? What if want to install 4.8.x and Qt 5?

@Peter: You are correct, there is something wrong in the MinGW package as we also notified in the mailing lists. We will provide a new installer. Others packages seem to be fine.

KarlNapf says:

Luca: All the meego guys left Nokia ages ago, the Symbian guys were fired last year and now the Trolls are almost out of the door. I doubt there is anybody left in Nokia that can actually do an update for the SDK.

Mariusz says:

Some nasty ones do not belong to the 200 chosen ones (QTBUG-26013, QTBUG-25896).

David says:

What about visual studio 2012 support? When will it be supported?

@Mariusz: We took in all fixes from the 4.8 branch. Best way to get bugs fixed is to either fix yourself or pay someone to fix. Naturally we are also continuously fixing bases on the priority, but many times a fix may also cause other issues. So especially in relatively mature 4.8 it may not be a good idea to fix at all.
@David: We have been experimenting with VS2012 a bit and so have some others. It will be supported at least with Qt 5, possibly also with 4.8.

Torben Dannhauer says:


I’m a commercial user of Qt and also would like to upgrade to VS 2012.

Since the beta of VS 2012 is out there for long time, and the required changes are limited (see http://stackoverflow.com/questions/12113400/compiling-qt-4-8-2-for-visual-studio-2012), it should be possible to introduce VS 2012 support into Qt 4.8 quickly within this month.

Especially due to the improving c++11 support (by the quaterly compiler updates) I suppose lots of people are interested in VS 2012 – you should’nt miss that point.

Steve Walker says:

“Best way to get bugs fixed is to either fix yourself or pay someone to fix. ”

So in other words the open source version of Qt is no longer supported by Digia. As the new owners of Qt I think you need to do a little more than simply package up external contributions to Gitorious.

anonymity is great says:

@Steve Walker: the phrase you quote is a statement that holds for any open source project! I use it myself for my open source projects. You should also read his next sentence: “Naturally we are also continuously fixing based on the priority”. So be confident: the open source version of Qt will still be supported by Digia.

Josh says:

I got a similar error as Peter when compiling SMPlayer, although I compiled it myself using Mingw-w64 4.7.1. I had to fix the Platform.h in Javascript and now this crap comes up.

binrcc.exe -name icons icons.qrc -o releaseqrc_icons.cpp
process_begin: CreateProcess(NULL, binrcc.exe -name icons icons.qrc -o releaseqrc_icons.cpp, …) failed.
make (e=2): The system cannot find the file specified.
mingw32-make[1]: *** [release/qrc_icons.cpp] Error 2
mingw32-make[1]: Leaving directory `E:/Buildsys/svn/smtube/src’
mingw32-make: *** [release] Error 2

Alessandro Portale says:

@Luca: For Qt/Symbian development, I suggest sticking with the current Qt Creator 2.4 version wich comes with the SDK. The Symbian support there was on its peak and tested. Since we did not have a dedicated Symbian maintainer, anymore, Symbian support biologically degraded in 2.5 and was completetely gone in 2.6.
In order to get a Qt 4.8 Symbian SDK, you would have to ask Noka that at developer.nokia.com. Sorry for not really being helpful, here :/

Josh says:

Qt 4.8.2 works fine with the same compiler so I’m not sure why with 4.8.3 it gives that error. rcc.exe is present in the bin directory. Peter was using the precompiled one but I compiled it from source with a different MinGW toolchain and get the same error…

Josh says:

So, for some reason with MinGW it tries to execute rcc.exe from a subfolder called ‘bin’ in the current working directory instead of Qt’s bin directory. Other executables like moc.exe and uic.exe execute from Qt’s bin directory. Say if make/mingw32-make is executing in ‘C:fooprojectsrc’ it tries to execute ‘C:fooprojectsrcbinrcc.exe’, which obviously won’t exist.

Joerg says:

Also when building Qt 4.8.3 using mingw the package becomes unusable because of the rcc eror (as Josh and Peter stated).

Joerg says:

I found the “bug”. There is a missing line in the mingw qmake configuration.

Add following line to “mkspecswin32-g++qmake.conf”:


… and all will work!

Josh says:

Nice catch, Joerg.

Andrey says:

But threre is a bug for mingw version. If I compile Qt 4.8.3 from source and then try to compile my own project I see gcc flags -fno-exceptions -fno-rtti. While configuring Qt I see “Exceptions – yes, RTTI – yes”.

Boris Barbulovski says:

I have similar issue compiling code that has exception handling. I was using official build 4.8.3 mignw.

Josh says:

Andrey: It could be the default behavior has changed.. add ‘rtti exceptions’ to CONFIG in your .pro file.

Sina says:

Qt 4.7.4

Nick says:

I couldn’t build MySQL, PostgreSQL plugins and Qwt library on Windows using MinGW “out-of-box”. I tried to add simpliest main() function to *.cpp files. Everything seemed to go fine, but only *.a files for SQL plugins were created (without *.dll).
Then i commented out line


from mkspecswin32-g++qmake.conf file and all needed plugins and libraries had been built successfully.
What does line “load(device_config)” mean? I didn’t find this line in mkspecswin32-g++qmake.conf file of Qt 4.8.2.

Sorry for my English 🙂

Rajneesh says:

thanks Joerg s your suggestion helped to resolve rcc.exe issue

Andy Brice says:

It is a pain that I can’t get 4.8.3 from the SDK and I can’t tell the 4.8.3 Mac binaries installer where to put the binaries. Grrrr.

Andy Brice says:

BTW it took approx 24 hours to build Qt 4.8.3 on my Mac Mini! That is without the examples.

Commenting closed.

Get started today with Qt Download now