Replace @BUNDLEIDENTIFER@ in Info.plist

Change-Id: I34aa77fc51b1ae4d7941f01fcb20236250454d19
Reviewed-by: Gabriel de Dietrich <gabriel.dedietrich@digia.com>
Mac Style: Fix non-native menubar item spacing

Unfortunate consequence from inheriting from Common style instead of
Windows style.

Also, a font entry missing in QCocoaTheme.

Task-number: QTBUG-36224
Change-Id: I560494b1727734671478f70ee1ba800d21c916ca
Reviewed-by: Jens Bache-Wiig <jens.bache-wiig@digia.com>
fix VS 2010 project file generation for release mode

VS 2010 doesn't denote "no debug info" as "None" but as empty tag.
This fixes a regression introduced by
7c3efdfb6ad72955543128a5a13e3f45ef3ee7af.

[ChangeLog][qtbase][qmake] fix VS 2010 project file generation

Task-number: QTBUG-35610
Change-Id: I18ae69a842d0b679a781f8d24c026d422da3a857
Reviewed-by: Andy Shaw <andy.shaw@digia.com>
Don't allow the QLibraryStore to be recreated during shutdown

When QtCore's global destructors are run, they delete the global
QLibraryStore qt_library_data and set the pointer to null. If something
happened to call QLibraryStore::instance() later, it would be recreated
and then weird things might happen. So prevent that from happening.

That usually cannot happen, since the only thing that can run after
QtCore global destructors are other QtCore global destructors or global
destructors from libraries that do not depend on QtCore. So we're
reasonably safe. There are two conditions in which something could run
after QLibraryStore::cleanup() and still try to access QLibraryStore:

1) indirect dependency, like a global destructor from a library that
doesn't depend on QtCore running code from another module that does.

2) static builds of Qt modules. In that case, the order of the global
destructors is totally arbitrary and we could get one from a module that
depends on QtCore running after QtCore's. That is the case from the bug
report.

Task-number: QTBUG-36294
Change-Id: Id199671275fd2535acf2d158857ce46b474e579b
Reviewed-by: Kai Koehne <kai.koehne@digia.com>
Reviewed-by: Tim Jenssen <tim.jenssen@digia.com>
Add Qt 5.2.1 changelog

Change-Id: I0390aa8ff05270a8b6fe63e729b3f45dcc05275e
Reviewed-by: Simon Hausmann <simon.hausmann@digia.com>
Updated the list of examples tagged for Android

Tested the examples that are tagged for
user experience and relevance for mobile devices, and
updated the list accordingly.

Task-number: QTBUG-34805
Change-Id: I1ccd23fa626deb42c0fea4e03a2bf7a8dd2a856c
Reviewed-by: Eskil Abrahamsen Blomfeldt <eskil.abrahamsen-blomfeldt@digia.com>
move qprocess changelog entry to windows section

Change-Id: I0b0475ddd72491cf7b2cef304c434d2311640b84
Reviewed-by: Joerg Bornemann <joerg.bornemann@digia.com>
add buildsystem changelog

Change-Id: I84ad3008b7c8431e0874e51b0cdfb677b7ffcb8a
Reviewed-by: Joerg Bornemann <joerg.bornemann@digia.com>
Doc: Added more information about the WriteOnly mode

Task-number: QTBUG-34336

Change-Id: I4a9995dde400145cb1e33e625715eea8aaed3191
Reviewed-by: Topi Reiniö <topi.reinio@digia.com>
Doc: Remove section on how build the MySQL driver for MinGW users

The section is clearly outdated. It references MinGW from mingw.org, which
we don't support anymore. With a more modern MinGW you can just use the
recipe to link against the prebuilt binaries the same way we do describe
for MSVC.

Task-number: QTBUG-17268
Change-Id: I15b96fd328605b60d1494a703b9005e2c16aea39
Reviewed-by: Venugopal Shivashankar <venugopal.shivashankar@digia.com>
Reviewed-by: Jerome Pasion <jerome.pasion@digia.com>
X11: build again on Linux distros that don't have XInput 2.2

fixed1616ToReal is needed by the XI2 tablet event debugging added in
ecf11d62fc6f57cccf6f3326e768b1c7cabbd0b3, so it needs to be available
if tablet events are supported and XI 2.2 events are not (older Linux
distros).

Change-Id: Id763d585790a9f037abc408dfba4ab5eec6dd421
Task-number: QTBUG-36437
Reviewed-by: Laszlo Agocs <laszlo.agocs@digia.com>
Reviewed-by: Wolfgang Bremer <wbremer@blackberry.com>
Merge remote-tracking branch 'origin/release' into stable

Change-Id: I4680723bef393a15d5aa63b9dd7d5fbb599bd9fa