Task-number: QTCREATORBUG-2003

 * Fix displayed shadow build location
 * Fix shadow build location used by newly set up shadow builds

Task-number: QTCREATORBUG-1599
Reviewed-by: dt
(cherry picked from commit 1d8e1760)

Task-number: QTCREATORBUG-1597

 * Fix displayed shadow build location
 * Fix shadow build location used by newly set up shadow builds

Task-number: QTCREATORBUG-1599
Reviewed-by: dt

We only have one page there, so there is no need for the
side widget.

Tasknumber: QTCREATORBUG-1149

Reviewed-by: dt

Show the import wizard on all imports. This eases import of
shadow builds at non-default locations.

Task-number: QTCREATORBUG-1069
Task-number: QTCREATORBUG-1068
Reviewed-by: dt

Fix possible crash on import of projects into creator with
only one valid Qt version set up.

Reviewed-by: dt
Task-number: QTCREATORBUG-1017

 * Handle shadowbuild directories
 * Refactor the code

Reviewed-by: dt

... use it.

Reviewed-by: dt

Do this as part of the ProjectLoadWizard

... when creating a new project without any Qt version being
available

 * Ease cross device development by introducing 'targets' which
   group build- and runsettings that are valid for this one target

 Most of the kudos for the code review go to dt. Con, thorbjorn,
 ckandler and others did also review parts of this patch.

Reviewed-by: dt

QString: Use QChar where appropriate.

  * Use id() for methods returning a string used to represent
    some type of object.
  * Use displayName() for strings that are meant to be user
    visible.
  * Quieten some warnings while touching the files anyway.
  * Move Factories to their products in the plugins where that
    was not done before.

Reviewed-by: dt

That is we actually parse the mkspec and evaluate QMAKE_CXX (and a few
other variables) to figure out the correct mkspec. This makes using
custom mkspecs easier and is also cleaner. I also changed mkspec() and
mkspecPath() to behave a little diffrent, essentialy mkspec() will
return only the name (the actual dir name) of the mkspec. That is in
general not sufficient for passing on to qmake. mkspecPath() only
returns the correct path to mkspecs/default.
Hopefully I haven't broken WinCE/Maemo/MinGW.

Reviewed-by: dt

Builds, but I'm pretty sure it doesn't *work* :)

Rationale: The concept of a "Qt Dir" is dead ever since Qt can be
installed. Specifying the qmake location otoh makes it possible to
unambigously detect all parts of a Qt installation.

Don't add -spec foo to the additional Arguments if foo is the same as
the default mkspec. This makes the common case better, while breaking if
you have QMAKESPEC set in teh environment and used -spec foo to override
it.

We add each command line argument to the Additional Arguments

One less need for qmakestep.