almost too simple to be right, given the TODO ...

- parse .qmake.cache, remove workaround for not doing it
- look for the mkspecs in all the places qmake would do
- use the passed in properties instead of QLibraryInfo to find the qt
  data dir
- fix loading of generic features from within os-specific ones with the
  same name
- add multiple inclusion guard for features (including what seems to be
  a bug in qmake ...)
- misc cleanups and beautifications

qmake does so.
of course, in the longer run we need to get rid of this at all, but this
would require quite some reviewing of side effects.

to be able to share the option object among evaluators, it is passed by
pointer.

only field_sep stays static and becomes a string - that's effectively
just a cache to avoid repeated construction.

it's still static at that point, though.

non-inline implementations in a header? feh!

(the rest seems to have evaporated over time or never existed in the
first place)

it's redundand

... which is also what qmake does

actually use evaluateFeatureFile() instead of hand-crafting stuff

it's a bad idea to conditionalize a cleanup on a completely unrelated
variable.

Reviewed-by: dt

Unblock COM reading. Ensure process is started only once. Read out
registers. Read gdb memory request properly.

Fix the use of appendPlainText for automatic scrolling.

Reviewed-by: Daniel Molkentin

The compile-time solution introduced by 3a084ae8
was felt by some to be too intrusive, so I've integrated the check for
changes to QObjectPrivate into the auto test.

Reviewed-By: TrustMe

- Added auto test for QMap.
- Qt::UniqueConnection is not actually a connection type, so we
  don't treat it as one.
- The definition of QObjectPrivate keeps getting out of sync, so
  there now is a "static assertion" that causes a compile error
  when QObjectPrivate's size changes.

./bin/qtcreator: 3: Syntax error: "(" unexpected

paragraph, even when it has several lines.

First, there's no $( ) for subshells. You have to use backticks.

Second problem, "VAR=value exec command" doesn't work. Split into
variable setting, exporting and then exec'ing the program.

Third, Solaris doesn't come with readlink, so parse the output of ls -l.

Reviewed-By: TrustMe

Reviewed-By: TrustMe