It was badly positioned esp. in OS X and Windows.

Reviewed-by: kh1

Reviewed-by: Alessandro Portale

Fix README, some spelling errors, remove contractions,
exclamation marks, correct some plural forms, join split messages.
Add QCoreApplication::translate to non-Q_OBJECT-classes.
Fix some lupdate warnings about discarding meta-data (//:).

Add more error messages to processes run for toolchain detection.
Move Windows-specific code to dbgwinutils, remove inclusion of
<windows.h>. Fix MinGW gcc 4.5 warnings.

Reviewed-by: Alessandro Portale

Could not be tested with actual QML project yet.

Reviewed-by: kh1

Reviewed-by: Alessandro Portale

Give warnings about failures to be able to fix things/timeouts on
slow machines. Pass on arguments correctly on Windows.
Make sure processes are killed on timeouts.

Reviewed-by: kh

Also document remote gdbserver adapter's signal.

Was renamed weeks ago, somehow came back.

Parse script output instead.

Done-with: kh1

 * Explicitly set signing mode to SelfSigned if not mentioned in the
   .user file
 * Do not use c-style casts.

Reviewed-by: dt

QString::isNull() vs. isEmpty() discrimination is a time bomb ...

 * Make sure we have a display name set for targets when restoring
   from Qt creator 1.3.1 .user files.

e.g. DEFINES+=bla on the qmakestep command line now work

Task-Nr: QTCREATORBUG-2091

There's a UI in qml/customexec/cmake/qmake run configs for choosing the
debugger languages (C++ and QML). The default for all except .qmlproject
is only C++, so default debugging behavior is the same. However, if the
user wants to do simultaneous debugging with two languages, or only
debug QML, they can select the languages from Run Settings and it will
be remembered.

Reviewed-by: hunger

Reviewed-by: Alessandro Portale

Apparently, the sender can still be null even though it's deleted
via deleteLater().

This is needed for sourve packages, but interferes with binary ones.