[Interest] Qt 5.5 WinRT x64 VS2013 applications fail WACK Direct3D tests

[Kalinowski Maurice]

Hi,

would you be able to tell us, which API calls are failing on your side?

We are aware of Trim() causing troubles against the Windows 10 certification and are aiming to have this resolved with Qt 5.6. However, it should still work with VS2013/8.1 and then have your app also deployed on Windows 10 itself.

If there is anything else on your side, please let us know.

D3dcompile_qt was needed in older versions before D3DCompile was present. Hence we could remove that library at some point in the past.

BR,
Maurice

From: interest-bounces+maurice.kalinowski=theqtcompany.com at qt-project.org [mailto:interest-bounces+maurice.kalinowski=theqtcompany.com at qt-project.org] On Behalf Of Alexander Tkachenko
Sent: Freitag, 18. September 2015 14:01
To: interest at qt-project.org
Subject: [Interest] Qt 5.5 WinRT x64 VS2013 applications fail WACK Direct3D tests

Hello!

I downloaded latest Qt 5.5 x64 WinRT VS2013 binaries, created basic QWidget application and converted my Qt project to VS project by executing "qmake -tp vc .pro "CONFIG+=windeployqt"". The VS2013 project could be compiled and launched easily but both Windows Application Certification Kit Direct3D feature tests failed. I also have tested Several Qt example projects on Win 10 VirtualBox and Win 8.1 PC with the same result. Tried all these things with Qt 5.5 WinRT x86 VS2013 which I've built from sources w/o success.
On the other hand I installed Qt's QuickForecast application from Windows Store and it passed all WACK tests. The only significant difference I noticed between both packages is d3dcompiler_qt.dll in QuickForecast package folder. This .dll is missing in Qt 5.5 x64 WinRT VS2013. There is a d3dcompiler_47.dll but when I put it into package I got another WACK fails connected to restricted APIs in d3dcompiler_47.dll.
Is there any way to enable Direct3D features support and passing WACK tests with Qt 5.5 WinRT x64 VS2013?
I really appreciate any help.

Best regards,
Alexander Tkachenko
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/interest/attachments/20150921/c0ff9da4/attachment.html>