Building Qt projects with Qmake
Building Site
Qt's own build system Qmake is often overlooked for larger projects, but many experienced developers appreciate Qmake support for shadow builds and pre- or post-build dependencies.
Qmake, the build system originally developed by Trolltech for Qt applications, often goes unnoticed. Many developers are happy to use the combination of Qmake and the Qt library for small- to medium-sized projects. But as the projects grow, many Qt developers suddenly switch to the Qmake alternative Cmake, which originated as the build system for ITK (the Insight Segmentation and Registration Toolkit).
The reason most often heard for neglecting Qmake is that it is simply unsuitable for many tasks. In the KDE project, for example, Cmake is the tool of choice for compiling large amounts of source code. (Other build systems, such as Autotools, Ant, and the like play a very small role in Qt development because of the increased integration overhead.) As this article shows, however, Qmake can do so much more than most developers realize.
Qmake versus Cmake
Both Qmake and Cmake create a makefile from a project file, which make and make install then reference. Although the basic approach is similar, the syntax of the build files is very different. The differences between Qmake and Cmake are best illustrated with a Hello World program that includes the component files main.cpp, hellowindow.cpp, hellowindow.h, and hellowindow.ui.
[...]
Buy this article as PDF
(incl. VAT)