... because the files are installed even when packaging is disabled.

Reviewed-by: kh1

Reviewed-by: kh1

Reviewed-by: kh1

This broke after the introduction of a deploy step type.

 * Move and rename the enum
 * Add Q_ENUMS macro

Reviewed-by: dt

Task-number: QTCREATORBUG-1636
Reviewed-by: kh1

Task-number: QTCREATORBUG-1686
Reviewed-by: ck

Reviewed-by: kh1

Reviewed-by: ck

Fixes: - react on build/ run configuration changes
       - now notices environment changes, like switching Qt versions
       - start button is now only shown if we have a valid qemu runtime
       - enabled/ disabled state works properly when loading a project

Task-number: QTCREATOR-210, QTCREATORBUG-1252, QTCREATORBUG-1082
Reviewed-by: ck

Fixes: - react on build/ run configuration changes
       - now notices environment changes, like switching Qt versions
       - start button is now only shown if we have a valid qemu runtime
       - enabled/ disabled state works properly when loading a project

Task-number: QTCREATOR-210, QTCREATORBUG-1252, QTCREATORBUG-1082
Reviewed-by: ck

Reviewed-by: kh1

Reviewed-by: kh1

Task-number: QTCREATOR-207
Reviewed-by: ck

Renamed RunConfiguration::configurationWidget to
createConfigurationWidget.

Reviewed-by: dt

Reviewed-by: kh1

Reviewed-by: ck

Reviewed-by: ck

Reviewed-by: kh1

... use it.

Reviewed-by: dt

This is a big change touching almost all of our .pro file parsing.
With this patch we only evaluate once exact for all needs and once
greedy for the filelist. That is the qt runconfigurations don't have own
evaluaters but reuse the project wide exact evaluation.

We reevaluate if the user changes the build directory, the qmake
buildconfiguration or the qmake arguments. That is if you open src.pro
(or projects.pro) of qt with a shadow build you still don't get all the
files, but after correcting the build directory, we reevaluate the .pro
files and find all files. So for a suitable definition of fixed, that
bug is now fixed.

We now get the exact defines of all .pro files instead of all defines for all
buildconfigurations. We still don't distinguish in which
.pro file a DEFINE is set. So the code model now knows about all the
defines set for the given configuration but not for which files it is
actually set. Also that includes all DEFINES set in .qmake.cache or the
mkspecs. This means all defines from .pro files should now work.

The intial loading is still synchronous. I haven't looked into it to
deeply, but it seems possible to make it also async.There are probably a
few issues which need to be solved fist.

Also due to the asynchronous nature of the code, the executable is
updated a few seconds after actually changing the build configuration

Reviewed-by: kh1

Reviewed-by: ck

Functionality depends entirely on the active start-up project, all other
projects should have the the button disabled if they have no Maemo run
config or the the run config is not the active on.

Reviewed-by: ck

Since we use addAutoReleasedObject we would rather unclean call the
class destructor.

This makes the qemu run button appear/ disappear once we add a maemo
target to an existing project.

Reviewed-by: Tobias Hunger

  ... when simulatorPath is unset.