QtCreator

Qt Creator 2.7.1 released

We take today’s Qt 5.1 beta release as an opportunity to push out some fixes to Qt Creator 2.7.

Around 40 bugs reported on our bugtracker have been fixed, so if you wonder if your favorite issue is one of them you might want to check out the list of “Qt Creator bugs that have been closed as ‘done’ for 2.7.1″ on our bug tracker. And of course there were other bugs fixed that do not appear on that list, so you should definitely check Qt Creator 2.7.1 out.

Download Qt Creator 2.7.1

Qt Creator 2.7.0 released

We are happy to announce the Qt Creator 2.7.0 release today, which comes with loads of new features, improvements and bug fixes.

C++ support in Qt Creator got even more improvements for C++11, like handling of alignof, alignas and noexcept, brace initializers, and more lambda fixes. Also, if Qt Creator cannot find out if your tool chain expects C++11 or C++98/03, it defaults to C++11 now, for a better out of the box experience. Also there are improvements on the refactoring actions side, for example quick fixes for adding getters and setters for class members, and for adding the getters and setters that are specified in a Q_PROPERTY.

QML support got lots of fixes for Qt Quick 2 in the code editor, and there was a lot of work done to make Qt Quick Designer work with Qt Quick 2. Please note though that the Qt Creator standalone binary packages are based on Qt 4 and do not provide the necessary Qt Quick 2 based external worker tool (which of course needs to be built with Qt 5). For now you either need to compile Qt Creator with Qt 5 yourself, or at least compile the qml2puppet yourself with Qt 5 (qt-creator/share/qtcreator/qml/qmlpuppet/qml2puppet) and put that into qtbase/bin of your Qt 5 install (and make sure that your project uses a Kit that uses that Qt version). Or you wait for Qt 5.0.2 packages that will contain a Qt 5 based build of Qt Creator again.

On the BlackBerry support side, we got a new settings page, which allows to easily generate Kits (and the necessary Qt version and compiler information) from an NDK path, and helps users with registering and generating developer certificates and other files that are needed for uploading apps to their devices. Also the editor for bar descriptor files, which define application appearance and behavior, can now be switched between editing the pure XML and a graphical editor. There were many other improvements as well, for example regarding debugging on devices.

Experimental support for the (also experimental) QBS build tool was added to Qt Creator, and the binary packages now also contain it (in contrast to the prereleases), though it is disabled by default. To enable it, open “Help > About Plugins” (on Mac it’s in “Qt Creator > About Plugins”), tick the QbsProjectManager, and restart Qt Creator, no further downloads/installations are necessary. The Qt Creator sources themselves also come with QBS project files, if you were wondering which project you can open with it now ;) . If you want to build Qt Creator with QBS support yourself, you first need to pull in its sources: Qt Creator’s git repository now has QBS as a submodule, so “git submodule update –init && qmake -r && make” in the top-level directory of your git checkout should be all you need to do.

Of course this is only a very small part of the actual improvements that were done, but talking about all of them – Debugging, Android, VCS, FakeVim, just to mention a few – would be beyond the scope of the blog post. Even bookmarks got some love this time, thanks Vasiliy Sorokin :) . If you want to know more about changes in this version, you might want to have a look at our change log.

Open source download: Qt Creator downloads page (or the Qt Project downloads front page)

Qt Commercial customers find packages in the Customer Portal

Important note for developers for Madde: Madde support has been disabled by default in Qt Creator 2.7. Most functionality is available by default through the “generic Linux” support. If you still want to use the Madde specific plugin, you need to enable it: On first start of Qt Creator 2.7.0, run it with command line argument “-load Madde” (that is important, otherwise you will lose existing Madde settings like tool chains and Qt versions), then open Help > About Plugins and enable the Madde plugin.

Important note for people that turned off the QmlJSTools plugin manually: Qt4ProjectManager depends on it in Qt Creator 2.7, so you need to turn it on again to be able to open qmake projects.

Qt Creator 2.7.0 RC released

Today we published the Qt Creator 2.7.0 release candidate. Since the set of features is the same as for the beta release of course, I’ll just point you to the blog post by André about that, who summarized it quite nicely.  But of course we sat down and fixed lots of bugs, summing up to a total of 490 changes. Thanks to all who helped by testing, reporting bugs, debugging and actually fixing!

Just to mention a few things: There were lots of fixes to the C++ code model again,  with one fix that almost is a sneaked in feature: The C++ quick fix “Add Definition” now also works for non-member functions. Android support got some polish, like fixing kits when the used NDK changes. The kits received some more love in general, with around 30 fixes alone in the area of tool chains, Qt versions, devices and kit setup. On the debugger front, it’s for example now possible to use mini dumps on Windows. And Leena fixed the documentation all over the place, as always many thanks to her!

Users of the open source version of Qt Creator should jump over to the Qt Project downloads page, commercial customers find their packages in the Customer Portal.

Important note for developers for Madde: Madde support has been disabled by default in Qt Creator 2.7. If you still want to use it, you need to enable it, first run Qt Creator with command line argument “-load Madde” (that is important, otherwise you will lose existing Madde settings like tool chains and Qt versions), then open Help > About Plugins and enable the Madde plugin.

Qt Creator 2.7.0 beta released

We are happy to announce a prerelease of Qt Creator 2.7. This is intended to give some early impression of improvements and new features of the final release scheduled to ship at the end of March, and also as a way to gather last minute user feedback.

All in all we are looking at more than 1300 changes by 63 developers. The changes with most user visible impact are recorded in the ChangeLog.

Let me highlight a few areas:

On the C++ support side we see better, but not yet full support for C++11. The new keywords alignof, alignas and noexcept are handled, as are ref-qualifiers in function declarations, “>>” in template parameters, some more cases of lambda captures, and a few more. The biggest addition is support for uniform initialization (a.k.a. brace initializers). In cases where the build system does not provide enough hints we now assume the code is C++11, not C++98/03, giving generally a better out-of-the-box experience. Before questions arise, yes, this is still our trusty old code model, a switch over to clang is still hampered by the performance impact this would have.

Screenshot of Qt Quick DesignerOn the QML side there was quite some work to make the Qt Quick Designer work with Qt Quick 2. Note, however, that the binary packages are based on Qt 4.8 and therefore do not contain qml2puppet, the external process that is responsible for rendering Qt Quick 2. You can build it yourself from source (qt-creator/share/qtcreator/qml/qmlpuppet/qml2puppet), or wait for the Qt 5.1 release. As the other Qt 5 packages, this will come with a Qt 5 based Qt Creator build. Qt 5.1 will also contain Qt Quick UI components, making the Qt Quick Designer more fun to use.

The “Kits” (i.e. working sets of device, compiler, debugger, and Qt version settings) introduced with Qt Creator 2.6 have proven to be a pretty flexible foundation for a wide scope of use cases, especially in the cross-development area. It is now e.g. possible to use certain custom toolchains without the need to create a specific Qt Creator plugin and also easier to create ready-made custom setups. As a result, it will be possible to provide ready-built embedded Linux images again for the commercial licensees which have been missing in 2.6. The new flexibility came with a few rough edges in the UI, but the worst have been addressed by now. This is one of the areas where feedback from Real World use would be especially valuable.

Other than that there have been smaller and bigger changes across the board. There is, for instance, experimental support for the (also experimental) QBS build system, including .qbs files for building Creator itself, Merge Tool support in the git plugins, new templates for BlackBerry applications, a more straightforward way to visualize images and vector data in external viewers when debugging etc etc. I’d like to take the opportunity and thank Orgad for becoming the most active contributor, and on a more personal note Lukas for picking up the ball in the FakeVim arena, tying up the loose ends and doing all the grunt work of bringing it from the “good enough for me” to the “works well for others” state. Thanks, guys!

What now?

The commercial license holders can download packages from the Customer Portal, open-source users from release.qt-project.org or directly build from the 2.7 branch on Gitorious. Try it, and report back using the Bug Tracker. We are also reachable on #qt-creator on FreeNode IRC and the qt-creator@qt-project.org mailing list. Please do not attempt to report bugs in the comment section of the blog post or the web forum, chances are they won’t be visible to the people who might be able to fix them.

We will go into string freeze on Thursday next week and plan to have a first Release Candidate two weeks later.

A final heads up for the users of the Madde plugin: As the functionality is now mostly available using the Generic Linux approach, the plugin has been downgraded to “not loaded by default”. This has right now the effect that the related settings vanish and need to be re-entered after re-enabling the plugin. We will look into a solution for the final.

Qt Creator 2.6.2 released

Qt Creator 2.6.2 has just been released. A quick count yields 55 patches on top of 2.6.1, the majority of them of the Mostly Harmless kind, fixing usability and UI issues. Some serious issues got fixed, too, most notably the code editor freeze some people encountered on certain constructs in the C++ editor (see QTCREATORBUG-8472 and QTCREATORBUG-8532). The full change log is here.

Binary packages of stand-alone Qt Creator 2.6.2 are available the download site, sources are as usual accessible from gitorious, and last but not least it is part of the Qt 5.0.1 release.

Qt Creator 2.6.1 released

Today we released Qt Creator 2.6.1. It contains lots of bug fixes, and solves issues when using Qt Creator for Qt5 based projects. See the change log for details.

Get Qt Creator 2.6.1 from our download site. A Qt5 based build of Qt Creator 2.6.1 is also included in the Qt5 release today.

Qt Creator 2.6.0 released

We are happy to announce Qt Creator 2.6.0 final today. If you haven’t followed the pre-release blogs, I’ll summarize the highlights of the new version here.

The probably most apparent change, that affects basically every Qt Creator user, is that we introduce Kits as a replacement for what were Targets in 2.5 and earlier. There you were adding Targets to a project’s configuration, from a predefined set like Desktop or Remote Linux, which were then doing some predefined “magic” things on top of the build, run and deploy configurations that they contained. We went and generalized that into Kits: A Kit contains settings for which device type to develop for (like Desktop or Remote Linux), the sysroot, compiler, debugger and Qt version to use, and potentially a few more. You can define these yourselves, and add them to a project’s configuration, where they again contain sets of build, run and deploy configurations. That makes it easier for users to control their build and run environments, and to share configurations between projects.

To define Kits, open Build & Run in the preferences, define your compiler in the Compilers tab (or make sure they were autodetected), add your Qt versions in the Qt Versions tab, and finally switch to the Kits tab and add a kit that uses the previous settings. Then go to Projects mode and choose Add Kit to add that configuration to your project.

On the platforms front we have new experimental support for Android merged into Qt Creator from the Necessitas project. Please check on their pages for more information, a list of entry points has been collected on the Qt Project Wiki. Also new is support for QNX/BlackBerry projects. These are really great news, and lots of thanks go to all that made that happen. On the downside we had to drop support for Symbian from Qt Creator, because of missing maintainer.

Otherwise there are lots of new bigger and smaller features and improvements all over the place. I already mentioned a few in the beta release blog, other examples are full screen support on Mac OS Lion and later, that you now can write e.g. foo.txt:123 in Locator to directly jump to a line in that file, lots of fixes and additions to the qrc file editor, like directly opening and renaming files, direct rebuilding and cleaning of .pro file based subprojects, more C++11 fixes, highlighting of macro usages, and more.

Download from Qt Project (Change log)

Commercial licensees find Qt Creator packages on the Customer Portal

If you are wondering how Qt Creator 2.6 runs on Qt 5, our upcoming Qt 5 Beta 2 release will include Qt Creator 2.6 based on Qt 5.

Update: If you had problems installing on Windows XP, please try again, the installer has been updated with a fix.

Qt Creator 2.6.0 RC released

Qt Creator 30 Days Created vs Resolved

The last 5 weeks we concentrated on fixing lots of bugs in preparation of the 2.6.0 release. About 380 changes have gone into 2.6 since the beta release and the “Created vs Resolved Chart” of our bug tracker looks very nice ;)

The move to the Qt Project infrastructure for building our packages is also progressing nicely, with the result that the release candidate now also comes with installers for Windows and Linux again (not needed for Mac). Please report any issues you find with the installer on bugreports.qt-project.org, project “Qt Creator”, component “Installer”. Please also report any other issues you find with this release there, of course.

If you didn’t follow the 2.6.0 beta release, you might want to read the beta blog post, which gives an overview of the new features.

Download (Change log)

Note to Mac OS X Mountain Lion users: The application is not signed yet, to open it you need to right click and select “Open” from the context menu the first time you run it.

Qt Creator 2.6.0 beta released

This prerelease of Qt Creator 2.6 gives you a an early impression of the many new features and the bigger changes that we will introduce with this release. And of course it is your chance to give us last feedback and help us find bugs and problems :)

Let’s start with the most apparent change: We replaced what we called “Target” before in Qt Creator, with what we call “Kits”.

“Targets” were basically a setting for something related to the device type, e.g. “Desktop”, “MeeGo Device” and so on. They were fixed, hardwired into Qt Creator, and came with defaults for build settings like which tool chain and debugger and sysroot to use. Some settings were unclear how they were chosen (like the Qt version). Some combinations of settings were prevented, for example the available tool chains were reduced to the ones Qt Creator thought would work with the Qt version you chose. You’d add support for a “target” to your project in Projects mode, and build and run settings were set up with the defaults. Deviating from the defaults required manually changing all build and run configurations.

“Kits” basically specify which combinations of device, compiler, debugger, and Qt version (and possibly other settings) you want to develop for. They are user defined, and the set of options in the kits is extensible from (binary) plugins. You define kits through adding them in Tools > Options > Build & Run > Kits, where you then freely choose each individual settings value in the kit independent from all others (meaning that you can for example choose any compiler that you configured in Tools > Options > Build & Run > Compilers, independent from what Qt version you set). If Qt Creator thinks that a certain combination of settings will not work, it prints a warning, but it does not prevent you from knowing better ;) . You add support for a kit to your project in Projects mode similar to it was before with “targets”. You can change a kit to use different settings, and any change is automatically reflected on all projects that use that kit. Qt Creator sets up a default kit on first run, with settings derived from the tools found in your PATH.

 

Regarding new features, we merged both the Android support and the QNX support into Qt Creator 2.6. This is great news on the “platform support” side of things, and even more impressive because we did all the above mentioned refactoring regarding targets and kits simultaneously. Thanks to all that made this happen!

These new supported target platforms are unfortunately shadowed a bit by the fact that we also had to drop Symbian support because of missing maintainer.

New are also experimental support for Gerrit, which allows you to browse your current changes and browse the diffs or cherry-pick/pull directly from within Qt Creator, and experimental support for the ClearCase version control system. There have been lots of other smaller and larger changes and fixes, like compilation of single files for qmake projects, more fixes for C++11, and a UI for setting temporary breakpoints, just to name a few. You find the more complete changes list here.

All in all 75 people have contributed to this release (see the end of the changes file), a big Thank You to all of them!

Get binaries and source code from our download page.

Note to Mac OS X Mountain Lion users: The application is not signed yet, to open it you need to right click and select “Open” from the context menu the first time you run it.

Note to Windows and Linux users: We are currently in the process of moving the package build infrastructure to the Qt Project. Unfortunately we cannot offer you installers for this release, simply uncompress the 7z files and run the Qt Creator binary located in the bin/ directory.

Qt Creator 2.5.2 released

Qt Creator 2.5.2 contains only a single bugfix that is important to all Windows (7) users:

  • Fixed resource leak leading to regular crashes on Windows (QTCREATORBUG-7385)

So, if you are a Windows user of Qt Creator, I advise you to quickly go to our download page to get the new version. Everyone else can safely ignore this release.

The Qt Blog

Welcome to the new Qt blog! We have consolidated all the blog posts from the Qt Labs Blog with the posts from the Digia Qt Commercial blog. Our intention is to provide you with one area for all Qt development posts from our Qt experts.

As Qt enters a new era, we are working diligently to provide you with an ever-growing Qt Blog that includes projects, awesome ideas, tips and tricks and product info from our pool of very clever Qt developers.

This blog will be transforming as we move forward, so keep your eyes peeled for new developments.

Archives

Categories