I need that in the Qt4ProjectConfigWidget to decide whether I should
show a import label.

See commit d0340ee0,
which breaks it for Mac at least.

QMake contained a bug that -cache something where not copied to the
 # Command comment. So we can't reliable check whether it is still
 the same cache. That should be rarely a problem.

Use the mkspec of the qt version if none is specified in the additional
arguments. Also if given a relative path, try the source directory
first.

Importing the build settings now should never run the qmakestep.

We add each command line argument to the Additional Arguments

One less need for qmakestep.

Task-Nr: 257765

Hides the gory details, and in most cases the user doesn't care anyway.

It may be that a non-default Qt version provides documentation even if
the default one does not.

Fixes: 257970

Only connect in restoreSettingsImpl() not in the constructor.

Not finished 100%

Requires a lot of trivial forwarding.

Specially for FakeVim users out there who want an easy way to switch to
vim's default color theme on a dark brackground.

Also did a little cleanup.

Since that method actually checks if Qt is built 64bit,
not if MSVC is 64bit.

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.

There were both variants, with and without extra semicolon.

Bug was introduced when separating the version list into "Autodetected" and
"Manual" subtrees.

this also removes the bogus special casing of various
filename-containing variables inside the pro parser.

A project's existing .pro file could be added to the project, making
the .pro file appear twice in the project tree. This is sub-optimal
because

1. It does not make sense for the .pro file to appear twice.
2. Qt Creator crashes when trying to remove either of the duplicate
.pro files.

Added translation macros to some editor kinds.
Added possibility to translate names of editors in Open With context menu. Translation context is "OpenWith::Editors".

Merge-request: 808
Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@nokia.com>

E.g. cmake pops up a wizard then, the running of cmake can fail though.
Now you don't end i[ with a empty project then. The error reporting in
that case is not yet optimal.

Make Gui app wizard use Qt Designer wizard code to write the classes.
Remove the settings from the form class wizard page extension area and
add a settings page instead. Polish the designer plugin's structs to
parametrize class generation with QSharedData and settings code.
Export them and use them in the Gui app wizard.

Task-number: 256927