Reviewed-by: Tobias Hunger

Reviewed-by: Tobias Hunger

 * Report all commands that failed.

 * Add parser
 * Use it
 * Improve parser setup in Qt4 makestep
 * Add tests for the sbsv2parser

 * Do not implicitly set up a gnumakeparser as part of the
   abldparser.

 * Simplify logic while at it, too.

 * Export SBS_GCCE<VERSION>BIN containing the path to the GCCE compiler
   used.

Reviewed-by: Tobias Hunger

 * Update list of S60 header pathes to match up with what is put into the
   Makefile by QMake (minus ../tmp directories).

 * Add a DeployConfiguration class to hold settings related
   to deployment.
 * Add BuildStepsList to hold a list of buildsteps
 * Update BuildConfiguration to use BuildStepLists instead of
   manageing lists of buildsteps itself.
 * Update BuildManager to use BuildStepLists in its interfaces
 * Fix fallout introduced by API changes
 * Update .user file to new way of storing settings

Task-number: QTCREATORBUG-1427
Task-number: QTCREATORBUG-1428
Task-number: QTCREATORBUG-1811
Task-number: QTCREATORBUG-1930

Task-number: QTCREATORBUG-1224
Reviewed-by: aportale

Added support for passphrases for keys for Symbian OS

Reviewed-by: Tobias Hunger

We create a .sis package per leaf project now, deploy all of them and
start the executable for the runconfiguration that was selected. This
does not cover all use cases, but works for development.

Silent installation added to Sumbian's Run Configuration UI

Reviewed-by: Tobias Hunger

Creator crashes while Carbide has ownership over serial connection and Creator wants to use it as well

Reviewed-by: Tobias Hunger

 * Add buildstep to handle the deployment
 * Remove deployment code from the runconfiguration
 * Update .user files to add new deployment step into existing setups

Reviewed-by: Tobias Hunger

(cherry picked from commit b87f3fbc)

 * Should work better with errors that can happen during deployment
(cherry picked from commit 3d2e5667)

Move link handling code to outputwindow from OutputFormatter

Move createOutputFormatter to the RunConfiguration

That makes it easier for Qt4RunConfiguration et all.
This also fixes that each time a runcontrol was rerun a new
OutputFormatter was created without deleting the old one, thus
increasing the memory usage.

 * Should work better with errors that can happen during deployment

 * Add "Deploy" to BuildSteps::Type
 * Update UIs to handle deploy steps
 * Turn existing package creation steps from build type to deploy type
 * Move packaging steps into deploy steps when loading projects

Reviewed-by: dt

 * Move and rename the enum
 * Add Q_ENUMS macro

Reviewed-by: dt

To be able to connect to them in the debugger namespace.
Reviewed-by: dt
Reviewed-by: Christian Kandeler <christian.kandeler@nokia.com>

This replaces the (de facto) singleton engines and data handlers by classes
that are instantiated per run. The DebuggerRunControl will now create an
object of (a class derived from) DebuggerEngine that contains all the relevant
"dynamic" data.

DebuggerManager is no more. The "singleton" bits are merged into DebuggerPlugin,
whereas the data bits went to DebuggerEngine.

There is no formal notion of a "current" DebuggerEngine. However, as there's
only one DebuggerEngine at a time that has its data models connected to the
view, there's still some "de facto" notion of a "current" engine. Calling
SomeModel::setData(int role, QVariant data) with custom role is used as the
primary dispatch mechanism from the views to the "current" data models
(and the engine, as all data models know their engine).