* Make use of the ProjectConfiguration base class in the
   BuildConfigurations and update the factories accordingly.

Reviewed-by: dt

 * Use new BuildSteps interface (as seen in ProjectConfiguration).
 * Use new factory to construct/clone/restore them.

Reviewed-by: dt

doing it in 1.3 as well to avoid possible later conflicts

partly by removing unnecessary calls, partly by providing minimalistic
reimplementations.
this gives a quite incredible performance boost ...

qmake doesn't, either

that way the file formatting is better preserved.

just parsing it (once ...) ought to be sufficient. we don't need to
validate the syntax beyond that anyway.

Extract error message string from Trk, print proper message
when application crashes in run mode and terminate launcher.
Use same message in Debugger for consistency.
Reviewed-by: Robert Loehning <robert.loehning@nokia.com>Reviewed-by: John Doe

Conflicts:

	src/plugins/qt4projectmanager/qt-s60/s60devicerunconfiguration.cpp

Extract error message string from Trk, print proper message
when application crashes in run mode and terminate launcher.
Use same message in Debugger for consistency.
Reviewed-by: Robert Loehning <robert.loehning@nokia.com>Reviewed-by: John Doe

This reverts commit 607e5452.

Extract error message string from Trk, print proper message
when application crashes in run mode and terminate launcher.
Use same message in Debugger for consistency.
Reviewed-by: Robert Loehning <robert.loehning@nokia.com>

Add command line arguments to trklauncher. Add input field
to S60DeviceRunConfiguration and pass on to RunControl and debugger.

Reviewed-by: ck

To simply transmit the RunConfiguration

Reviewed-By: Tobias Hunger

 * Tips on welcome page still explained CTRL-6 for output mode.
   Remove this.

Use the filemanager instead

This user now also resides under /home on the device.

Chances are the user wants to select it anyway.

 - if there is no LastQtVersionUpdate we doesn't have a real timestamp and we are not able to check against this.
 - this will happen during/after installation with qt bundled versions

 Reviewed-by: Daniel Molkentin

Chances are the user wants to select it anyway.

 - if there is no LastQtVersionUpdate we doesn't have a real timestamp and we are not able to check against this.
 - this will happen during/after NDK installation

 Reviewed-by: Daniel Molkentin

This assumes that new Qt version entries will be put into
the System scope settings file.

They do what you expect them to do, that is build only a subtree.
The implementation is a little bit strange. We temporarly set the sub
node to be built on the BuildConfiguration, enqueue that
BuildConfiguration (which calls BuildStep::init()), and then reset that
temporary value.

A more general way would be to have the ability to extend
BuildConfiguration::buildProject() in a way that additional data can be
passed to the BuildSteps.

Task-Nr: QTCREATOR-5
Task-Nr: QTCREATORBUG-44

Task-Nr: QTCREATOR-269

they were remnants of the pro editor, which was removed long time ago.
they were still used for automatic editing of pro files, but were
totally overengineered for that purpose (removed 1300 LOC, added 40).

Instead note that it is invalid if trying to build and on the projects
mode pane.

Task-Nr: QTCREATORBUG-459

QMake passes those headers directly to gcc, so the user doesn't need to
include themselves.