<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type"/>
</head><body style="">
<div>
Hi Rainer,
</div>
<div>
</div>
<div>
as other members already stated out qmake has some limits - but:
<br/>These can be "hacked" ;-)
<br/>
<br/>We (our company) spent much time to discover different build systems and approaches -
</div>
<div>
where CMake was the most complicated and most work intensive solution.
<br/>
<br/>So we decided to use the long term and on all Qt platforms available qmake and
<br/>to use ONLY .pro files - even in Visual Studio 2005-2012 (thanks to the great VSAddin
</div>
<div>
this can be simply done by an export/import button to save/load .pro files).
<br/>
<br/>+ qmake .pro files are fully supported by VisualStudio, Eclipse and QtCreator
</div>
<div>
+ .pro files are simple and have a small footprint
</div>
<div>
+ extensible thanks to integrated (very simple) scripting functions and import of external files (.pri)
</div>
<div>
+ automatic dependenies for libs
</div>
<div>
+ version handling and execution of unit tests, pre- and post-build commands
</div>
<div>
+ can generate resource files (and with own commands even sources)
</div>
<div>
+ with a few tricks can used to automatically check out and include other dirs / libs / modules
</div>
<div>
+ automatically execute unit tests, create versioned file names, copy build files etc.
</div>
<div>
</div>
<div>
In our company we use qmake with some self written qmake functions (inside .pri include files)
</div>
<div>
to run a hughe build environment with fully automatic dependencies and execution of unit tests
<br/>directly after compile.
<br/>
<br/>Means: 591 .pro files (libs + apps + subdirs) and 23 .pri files (includes)
</div>
<div>
<br/>For a simple example how to automate things with qmake you can see an old blogpost here:
<br/>
<br/>http://www.3dh.de/3dh.de/2006/12/19/qt-automated-unit-tests-with-qmake/
<br/>
<br/>If you're interested, I can give you more details...
</div>
<div>
</div>
<div>
And yes: QMake is a really limited tool and will be replaced in the future by QBS or some other
</div>
<div>
system - but: For production environments it's a currently available and reliable tool,
</div>
<div>
working fine under Windows (in VC++ with the VSAddin) and Linux.
<br/>
<br/>QMake offers me some possibilities, VC++ cannot provide out of the box and thus is
<br/>the currently favorite tool to simply work with ONE .pro file for ALL platforms.
<br/>Getting CMake to this state is possible - but costs so much time and work,
<br/>that no one of my devs wants to use it.
<br/>
<br/>ciao,
<br/>Chris
</div>
</body></html>