Directly in the wizard and save that to the settings. Also give feedback
if a wrong path was entered.

By only providing a qtInstallDir variant

This splits up the edit and active settings. Let people try it and
report usability problems. I'm not 100% convinced of the layout either.

And react to changes to one of them.

Fixes a bug where the cmake plugin wasn't finding make, if the make
commands directory was added to path in the build environment.

If there are multiple files with the same name, then we try harder to
find the correct one. That is for jom and nmake we have a relative path
so we try to find a file which matches the relative path completly.
Instead of just comparing the last part.

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

out of source page.

Added possibility to translate "Add" and "Remove" buttons and "Clear system environment" checkbox in build settings of project.

Merge-request: 1141
Reviewed-by: Daniel Molkentin <daniel.molkentin@nokia.com>

This has still a few missing things, but this enough to start getting
some feedback. Missing are non qt projects, a solution for the
runconfiguration, a missing black line between the treeview on top and
the project settings at the bottom. Some flickering with removing/adding
widgets to the QScrollArea and not showing the expanded widget if the
Details button is right at the bottom.

Fixes a designer integration issue.
Task-Nr: 258315

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

Requires a lot of trivial forwarding.

There were both variants, with and without extra semicolon.

Scroll areas were added to the welcome mode and the project mode, to
make sure they don't limit how small Qt Creator can be made.

Done with mae

This reverts commit 33dd9dea.

mingw32-make.exe

That is we update all files with the new include and defines if we are
switching toolchains.

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.

That case is a corner case, it can happen if the user has run the codeblocks generator on the command line or if the user deleted the .user file. We mostly ask to get the user a chance to check that we set the correct generator. Or let him select the correct one if there are multiple msvc versions.

Note: This requires a cvs cmake and is not fully tested yet. This adds a
few missing pieces, so now opening new never built projects without a
.user file on systems with just one VS installation should work.

The CodeBlocks - NMake Makefiles generator combination is only available
in the cvs version of cmake.
This has not been extensively tested at all.

That is if using a cmake that outputs enough information. The necessary
patch for that was commited to cmake's cvs recently by Alexander
Neundorf.

Task-Nr: 250399

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

Task-Nr: 235965