GitLab

Reviewed-by: hjk

- Autodetect SDK by environment variable EPOCROOT and qt directory
below.
- Environment::appendOrSet/prependOrSet: Avoid duplicate entries
- Rename toolchain enumeration value
- Adapt S60ToolChainMixin to new GnuPoc setup, provide routines for
  all required variables.
- RVCTToolChain: Make RVCT detection smarter (Check for RVCT<v1><v2>BIN
  variable). Set all required variables in case of RVCTToolChain/GnuPoc
- QtVersionManager: Detect toolchain and Qt version properly, make S60
  device run config accept toolchain.
- Modify S60DeviceRunControl to execute 'make sis'
- Modify S60Devices::detectQt...() to check for Qt installed into SDK
  first and symlink as fallback.

 when not set to true in the .user-file.

 * Remove default Qt version from list of available versions

Brace for impact...

Happens e.g. in gdb sources itself: cp_canonicalize_string in cp-support.c

Note: If you are compiling with 4.6 but running against 4.7 then this
will result in a slightly buggy line edit.
Reviewed-by: Friedemann Kleint <qtc-committer@nokia.com>

And rename it to updateRunActions() again, since that function is
only called if the run actions actually change.

And port the Qt4ProjectManager to use that API for synchronization
between editors and the .pro file tree.

Reviewed-By: con

We used to fail back to the old format if the .qmlproject file
was invalid. Anyhow, this lead to weird effects ... better disable
it explicitly.

That no warning is shown right now when loading an invalid qmlproject
file is a bug in coreplugin.

task-number: QTCREATORBUG-611

Broke in f14c50da

 * Accidentally included a header not ready to commit yet.

OS

metatype redefinition