GitLab

Initial work on smart highlight of local symbols. For-statements and symbols genarated from a macro expansion are not yet highlighted.

Reviewed-by: dt <qtc-committer@nokia.com>

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.

The runner uses the applicationlauncher internally, which is now
exported from the projectexplorer plugin for that reason.

And add a sort of isEnabled functionality for run configs.
This doesn't do much yet though, and is not updated correctly either.

Since the actual tool chain is defined in the project, it
moved there from the qt version.

An empty default make target lead to an error.

Doesn't do anything else than showing the tool chains yet.

QtVersion provides possible toolchains that can be used by the
Qt version, e.g. winscw, gcce and armv5 for symbian-abld.

Passing the Project to the tool chain now. Not quite sure if I like it.

At the moment you need to close and reopen the preferences dialog though.

Will be used to find the "Qt in PATH" and "Qt from Symbian" versions.