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.

Also makes the code a lot smaller.

Since we can easily do that, just do it. No gurantee that we aren't
going to use rtti in the future.

- Add methods to obtain executable from the run configuration
  (to be used by Debugger later on)
- Log the file names and sizes
- Pass on CreateFile() errors.
- Rename class Adapter to Launcher.

Default to the baseName() of the .pro file.

It works, except that the code model doesn't get the rvct include
directories and defines yet. And you need to have everything for
rvct set up in your environment.

So now we use the values of the system environment as a backup
for build environment and system includes.

Reviewed-by: Daniel Molkentin

And adapt the device selection list.

This doesn't update at all yet, so you'll need to recreate the run
configuration or restart creator.

Not much error reporting etc yet. Application TRK needs to be
running on device.

One less need for qmakestep.

Create a new one and check if it's the same as the old one,
has the advantage that cached data doesn't need to be retrieved again.
It was that way before tool chain was moved to Qt4Project.

Tool chain type is saved in settings, make sure that the value doesn't
change between S60 enabled/disabled Qt Creator version.
Run configurations can change independent from the run settings
property page, re-add handling of signals.
Add some things to consider to the todo list.

Reviewed-by: dt

And if Qt version changed.

Transform the method in Qt4Project into a signal that is handled
by the run configurations themselves.

Not able to give it an additional passphrase yet, though.