Change-Id: I583c0ce503bf5db76c92362921352a6f388fa2c1
Reviewed-by: Daniel Molkentin <daniel.molkentin@nokia.com>

Change-Id: I62aa9a4033399ee7fc0b55952613657f124c8fb9
Reviewed-on: http://codereview.qt.nokia.com/2791


Reviewed-by: Qt Sanity Bot <qt_sanity_bot@ovi.com>
Reviewed-by: Eike Ziller <eike.ziller@nokia.com>

For out of source builds of Qt, the private headers are in
QT_BUILD_TREE (opposed to QT_INSTALL_PREFIX, or QT_SOURCE_TREE)

Change-Id: I3f22fdefffd43df4c71098425de4e44f561e6ab1
Reviewed-on: http://codereview.qt.nokia.com/900


Reviewed-by: Qt Sanity Bot <qt_sanity_bot@ovi.com>
Reviewed-by: Daniel Teske <daniel.teske@nokia.com>

Reviewed-by: con
Reviewed-by: Friedemann Kleint

QmlJSInspector does not depend on Qt private headers being available
any more: The needed private API files have been copied into the
QtCreator source repo.

... instead of running a sed script over a lot of files on each
version increment.

Should have been done earlier. 2.1.80 was burned in the pre-2.1.0->2.0.1
days, and we'd like to have odd subminor for 'working' and even subminor
numbers for pure cherry-picking release branches anyway.

Reviewed-by: kh1

We disabled the visible parts of the Qml support by default for the 2.0
release. Defining QTCREATOR_WITH_QML brings it back.

This hack should be removed as soon as 2.0 is shipped.

Reviewed-by: Daniel Molkentin

Users also can now explicitly set the path to the private
header files by passing "QT_PRIVATE_HEADERS=$PATH" to qmake,
or force qmake to ignore the plugins by passing in an invalid
/empty path.

Reviewed-by: con

Always write "Qt Creator" space. Also, make sure lines are
broken at 80 characters.

Reviewed-by: con

Details:  Requested in irc.