[Development] [5.7-beta] qtgamepad compile failure

[Tim Blechmann]

compiling the qt-5.7-beta tarball with msvc2013/64bit/static libraries,
out-of-tree build gives me:

---

cl -c -FIQtGamepadDepends -YuQtGamepadDepends
-Fp.pch\debug\Qt5Gamepadd_pch.pch -nologo -Zc:wchar_t -FS -Zi -MDd
-D_HAS_EXCEPTIONS=0 -GR -W3 -w34100 -w34189 -w44996
/Fd..\..\lib\Qt5Gamepadd.pdb -DUNICODE -DWIN32 -DWIN64
-DQT_BUILD_GAMEPAD_LIB -DQT_BUILDING_QT -D_CRT_SECURE_NO_WARNINGS
-D_USE_MATH_DEFINES -DQT_NO_CAST_TO_ASCII -DQT_ASCII_CAST_WARNINGS
-DQT_MOC_COMPAT -DQT_USE_QSTRINGBUILDER -DQT_DEPRECATED_WARNINGS
-DQT_DISABLE_DEPRECATED_BEFORE=0x040800 -DQT_BUILD_GAMEPAD_LIB
-DQT_NO_EXCEPTIONS -DQT_GUI_LIB -DQT_CORE_LIB
-IH:\qt3rd\qtgamepad\src\gamepad -I. -IH:\qt3rd\3rdparty-builds\libpng
-IH:\qt3rd\3rdparty-builds\zlib -IH:\qt3rd\3rdparty-builds\libjpeg
-IH:/qt3rd/qtgamepad/include -IH:/qt3rd/qtgamepad/include/QtGamepad
-I..\..\include -I..\..\include\QtGamepad
-IH:/qt3rd/qtgamepad/include/QtGamepad/5.7.0
-IH:/qt3rd/qtgamepad/include/QtGamepad/5.7.0/QtGamepad -Itmp
-IH:\qt3rd\qtbase\include\QtCore\5.7.0
-IH:\qt3rd\qtbase\include\QtCore\5.7.0\QtCore -IH:\qt3rd\qtbase\include
-IH:\qt3rd\qtbase\include\QtGui -IH:\qt3rd\qtbase\include\QtANGLE
-IH:\qt3rd\build-Qt-5.7.0-beta-msvc2013-x64-static\qtbase\include
-IH:\qt3rd\build-Qt-5.7.0-beta-msvc2013-x64-static\qtbase\include\QtGui
-IH:\qt3rd\qtbase\include\QtCore
-IH:\qt3rd\build-Qt-5.7.0-beta-msvc2013-x64-static\qtbase\include\QtCore
-I.moc\debug -IH:\qt3rd\qtbase\mkspecs\win32-msvc2013 -Fo.obj\debug\
@C:\Users\Tim\AppData\Local\Temp\qgamepadmanager.obj.84524.8750.jom
qgamepadmanager.cpp
	H:\qt3rd\jom.exe -f Makefile.Debug all
h:\qt3rd\qtgamepad\src\gamepad\qgamepadmanager.h(42) : fatal error
C1083: Cannot open include file: 'QtGamepad/qtgamepadglobal.h': No such
file or directory
qgamepad.cpp

---

i know ci builds with dozens of configurations are impractical and
require a significant amount of buildserver resources. but it would be
great if tarballs could be tested with non-standard configurations ...
namespaced qt, static libs, out-of-tree builds, slightly older compilers
... all these configurations are often broken in released tarballs. i
suppose both qt devs and users would save quite some time and
frustrations, if these configurations could be tested as part of the
process of releasing a tarball.

cheers,
tim