Details
P1: Critical Description
Building Qt 5.5.0 on Windows 7 with MSVC2013 fails with:
[10926/10983] CXX obj\src\core\QtWebEngineCore.custom_url_scheme_handler.obj [10927/10983] CXX obj\src\core\QtWebEngineCore.browser_accessibility_qt.obj [10928/10983] CXX obj\src\core\QtWebEngineCore.process_main.obj FAILED: ninja -t msvc -e environment.x86 -- cl.exe /nologo /showIncludes /FC @obj\src\core\QtWebEngineCore.chromium_gpu_helper.obj.rsp /c ..\..\..\..\..\..\q\qtwebengine\src\core\chromium_gpu_helper.cpp /Foobj\src\core\QtWebEngineCore.chromium_gpu_helper.obj /Fdobj\src\core\QtWebEngineCore.cc.pdb d:\q\qtwebengine\src\3rdparty\chromium\ui\gl\gl_bindings.h(15) : fatal error C1083: Cannot open include file: 'EGL/egl.h': No such file or directory ninja: build stopped: subcommand failed. NMAKE : fatal error U1077: 'D:\q\qtwebengine\src\3rdparty\ninja\ninja.exe' : return code '0x1' Stop. NMAKE : fatal error U1077: 'D:\dev\vs2013\VC\BIN\nmake.exe' : return code '0x2' Stop. NMAKE : fatal error U1077: '(' : return code '0x2' Stop. NMAKE : fatal error U1077: 'cd' : return code '0x2' Stop. NMAKE : fatal error U1077: 'cd' : return code '0x2' Stop. NMAKE : fatal error U1077: 'cd' : return code '0x2' Stop. [compile] Ended: 09:54 06/07/2015
I'm doing a shadow build, without angle, and the config line I used is:
-opensource -confirm-license -platform win32-msvc2013 -mp -debug -shared -prefix E:\dist\qt5-5.5.0-vs2013\qt5-x86-shared-debug -opengl desktop -no-angle -nomake examples -nomake tests -no-compile-examples -skip translations -no-incredibuild-xge -sse2 -no-dbus -no-audio-backend -qt-sql-mysql -qt-sql-sqlite -icu -I D:\dev\icu\icu-55.1-vs2013\include -L D:\dev\icu\icu-55.1-vs2013\lib -I D:\dev\icu\icu-55.1-vs2013\include -L D:\dev\icu\icu-55.1-vs2013\lib -openssl-linked -I D:\dev\openssl\openssl-1.0.2c-vs2013\include -L D:\dev\openssl\openssl-1.0.2c-vs2013\lib OPENSSL_LIBS="-llibeay32MDd -lssleay32MDd -lgdi32 -lcrypt32 -lws2_32 -ladvapi32 -luser32" -nomake tools
I am attaching a custom config and build log of the failed build to assist you.
Could this be related to the header pollution identified in QTBUG-44240 
, it is slightly different though.