We are happy to announce the release of qbs 1.3.0 today. Qbs, or Qt Build Suite, is a general cross-platform build tool that uses a language similar to QML for project description. Qbs can be used for any software project, whether it is written in Qt or not and it simplifies the build process for developing projects across multiple platforms.
If you haven’t tried it out yet, we strongly encourage you to take it for a spin to see how convenient building with Qbs is! Check out the documentation for more details.
What’s new in qbs 1.3?
For this release, we have concentrated on improving the integration with Qt Creator. The main points are:
Source files can now be added to (and removed from) qbs products via the project tree, just as for qmake projects. Thanks to Thomas Epting for the initiative!
More care is now taken to reload a project only if it is really necessary.
In addition, reloading a project has become somewhat faster, particularly in the case where a project file was changed without introducing any semantic differences (e.g. whitespace changes).
We think that these items, combined with a number of important bugfixes, have improved the user experience of working with qbs in Qt Creator a lot.
What else is worth mentioning?
On the language side, it is now possible to set different profiles for particular products. This is important for projects that need to produce binaries for different architectures.
Also, we have once again reduced the memory footprint significantly.
Published Wednesday August 20th, 2014 | by Lars Knoll
20 years ago, Trolltech, the company that created Qt, was founded. One of its founding principles was to release Qt as free software to the open source community. In the early versions, this was limited to Unix/Linux and the X11 windowing system. Over the years, more and more platforms were included into the open source version of Qt.
At the same time, the licenses under which Qt was available evolved. The Qt 1.x source code was still released under a rather restrictive license. With Qt 2, we moved over to the QPL. Some years later, with Qt 4.0, Qt started to embrace the GPL v2, to remove some license conflicts between GPL-based applications and the QPL.
Trolltech was involved in talks with the Free Software Foundation (FSF) when the GPL v3 was created, and we added this license as an optional license for Qt after it was published by the FSF. Finally, in 2009 Nokia added LGPL v2.1 as a licensing option to Qt.
The spirit of all GNU licenses is about a strong copyleft, giving users rather strong access and rights to the source code of application and libraries. It was always meant to protect the users’ freedom to modify the application and underlying libraries and run the modified application.
Note: With Qt Creator 3.2 we drop support for OS X 10.6 (Snow Leopard). The technical reason for this is that Apple does not support any kind of C++11 on that OS version. Of course that does not affect on which platforms you can run your Qt applications on. But it is not possible to run the Qt Creator 3.2 binaries on 10.6, and it also is not possible to compile Qt Creator 3.2 on 10.6 with the tool chains provided by Apple.
Qt Weekly is back from vacation with a post from a guest blogger (*applause*). In this post, Lorenz Haas tells us how to link Qt classes in custom documentation that is generated by using Doxygen.
By mid-2008, Sebastian Pipping introduced doxygen2qthelp for generating Qt Compressed Help files (*.qch) via Doxygen. Already by the end of the year, it was successfully merged into Doxygen. While 184.108.40.206 still had some mirror problems, version 1.5.8 provided stable and comprehensive support for creating QCH files out of the box. See Sebastian’s announcement as well as David Boddie’s article in Qt Quarterly.
Since then, this feature – I guess – has been used a thousand, a million times. Nowadays, I personally can’t imagine working without it. This is because it integrates perfectly into my favorite IDE – Qt Creator. There I can use my own documentation for context-sensitive help that can be triggered by the F1-shortcut:
Published Wednesday August 6th, 2014 | by Lars Knoll
Over the last years, many changes have been happening in the Qt ecosystem. One of the biggest was the creation of Qt Project where Qt is now being developed as an open source project. The Qt Project was created to provide a space open for all to further develop and foster innovation for the Qt technology.
Qt has always been a commercial product. During the Trolltech days licensing income funded development of the product. While Nokia’s motivations were different, at Digia, our goal is to again make sure that Qt thrives for all industries, all companies, all users no matter what platform. That said, we need to make sure the business of selling Qt as a product is successful in order to fund its future development for the good of everyone in our ecosystem. The importance of Digia’s commercial business for securing the future of Qt cannot be underestimated as it drives Qt’s foundation and everyday operations. A look into the commit statistics shows that around 75% of all code submissions to qt-project.org come from Digia employees. In addition, Digia manages the release process and the CI and testing infrastructure, thus covering more than 85% of the costs of developing Qt. Read more…
As the dog days of summer carry on, we at Digia, Qt are swatting down flies, mosquitoes and bees while we fan ourselves in the unusual summer heat currently striking Scandinavia … in Oslo … at least.
Meanwhile, on a cool note, the Fun Propulsion Labs at Google announced last week that, VoltAir a single and multi-player game built with Qt is available for download via the Google Play Store and as open source software. Coolbeans!
VoltAir was developed to provide an example of a C++ game designed for both Android and Android TV and the folks at Google also tested it on Nexus 5, Nexus 7, Moto X by Motorola, Android TV, and some Samsung devices.
Check Out VoltAir (Courtesy of Google Developers – YouTube)
We are happy to announce the Qt Creator 3.2 beta today. So you can already check out the many improvements we have done for the upcoming 3.2 release, and, not to forget, give us feedback on what we have so far. We mostly concentrated on stability and improvements, so no completely new platform supported this time, sorry . I’ll randomly highlight some of the changes here, but you should probably check out our change log as well for a more thorough overview, and just download the binaries and try it for yourself.
It’s almost a month since we gathered at the Estrel Conference Center to spend two days talking about Qt, where it is and where it’s heading.
The Summit started off with Lars Knoll giving the state of the project speech, which included status updates from various maintainers. The whole opening session can be watched on Youtube. One thing to raise from Lars’ speech is the need to unify Qt, to bring all Qt users closer to each other.
The two days contained over forty sessions on matters ranging from the use of box2d with QML to two sessions on QtCore. You can find many of the session notes from the Summit schedule page. And the more technical topics have threads on the Developer mailing list, which you can find from the list archives (search for threads marked QtCS).
Over 40 sessions in two days
The weather in Berlin was exceptionally hot, bordering on uncomfortable outside. Luckily the conference center had good air conditioning. However during the evening event we could enjoy the warmth outside in the garden. The setting was very good for continuing the discussions that started during the day. The hardiest participants continued their discussion at the hotel lobby bar after the official evening event was closed.
A big part of events like the Contributors’ Summit are the coffee break and corridor discussions that take place in between sessions. The venue provided enough tables and a couple of good corners with benches to spend some time drafting the upcoming session agenda or working on the topics raised in previous sessions.
Coffee break application demo
A big thank you to all the participants and of course to our sponsors!
Qt Enterprise Embedded provides pre-built system images for a range of popular devices, like the Nexus 7 tablets and the BeagleBone Black. With these, you can make your device “boot to Qt” and be up and running with embedded development literally within minutes. But what if you want to try a device that is not among these reference devices of Qt Enterprise Embedded? Until recently, as an evaluator, you were basically out of luck. And even with an Enterprise license, you would have to rebuild the image from scratch for your device, a process that can take some time. Now, with the recent update of Qt Enterprise Embedded, there is another option available. If your device runs a recent version of Android, it is now possible to install the Boot to Qt stack directly into the existing Android system image; in effect taking it over. We call this method Android injection. In this blog post we will show how this process works in practice. We will use a device called the ODROID-U3 as our example.
The Qt Blog provides you with one area for all Qt development posts from our Qt engineering experts. It includes information on projects in the works, tips and tricks, technical release information and more from our pool of very clever Qt developers.