source:
http://blog.qt.digia.com/blog/2013/04/16/qbs-reached-mile-stone-0-3qbs reached mile stone 0.3<div qt-metadata-icons"="">Published April 16, 2013 | By <a fn="" n"="" href="http://blog.qt.digia.com/blog/author/jbornema/" title="View all posts by Jörg Bornemann">Jörg Bornemann
Qbs, our alternative
build tool, has reached a new mile stone. Since the last one in December, qbs has had the following improvements:
The whole codebase has seen a major overhaul. Experiments from theprototype phase have been removed. The API for the Qt Creator plugin hasbeen stabilized. The test suite has been extended to cover mostfeatures. On our internal test farm – the same that is used for QtCreator – qbs is tested on
Linux, OS X and
Windows every time thetesting infrastructure detects a new change in the repository.
Support for installing your built products has been added. To install your project to ~/foo/bar useqbs install --install-root ~/foo/bar
The project loading phase got faster. On my machine, the times togenerate the makefiles respectively create the build graph for QtCreator 2.7 look like this:
The running time of incremental null builds, that is determining thatnothing of your project has changed, look currently like this for QtCreator 2.7 (same machine with Windows/Linux dual boot):
The performance gain stems from the fact that qbs only has to checkthe timestamps of the project’s source files. It already knows thetimestamps of generated files from the previous build.
On Windows this approach gains us much more than on Linux because retrieving the file timestamps is so unbelievably slow.
Support for detecting changes of project settings has been improved. Changing properties like
cpp.defines will now get noticed and result in a rebuild of the affected products.
Last but
not least, Qt Creator 2.7 comes with an experimental Qbsproject manager plugin. It provides support for loading and building qbsprojects.
