Unable to compile on Visual Studio 2015 Professional

[Pasquale Granato]

Hi all,

i'm new on ANGLE development so I hope someone could help me with my problem.

I followed scrupulously the instruction here 

https://chromium.googlesource.com/angle/angle/+/master/doc/DevSetup.md

to setup my dev environment. The only thing different is that I'm using Visual Studio 2015 Professional.

At first I had a lot of errors caused by the warnings, so I disabled the flag "Treat Warnings as Errors" in projects properties.

Nonetheless I'm still unable to compile.

The first error in log (repeated many times) is:

 fatal error C1083: Cannot open include file: 'vk_layer_dispatch_table.h': No such file or directory (compiling source file ..\third_party\vulkan-validation-layers\src\loader\debug_report.c) 

Is there any know problem with Visual Studio 2015 Professional? Can someone point me to some updated guide to get a working environment?

Thanks a lot

Pasquale

[Jamie Madill]

Hey Pasquale,

Sorry to hear you're having trouble. You're running into an annoying defect in our GYP-based build that we haven't been able to solve. To work around the problem, build the target "vulkan_layer_utils_static" manually first, then the rest should build as expected. We're working on moving away from GYP to GN so hopefully this will be a non-issue soon.

--
You received this message because you are subscribed to the Google Groups "angleproject" group.
To unsubscribe from this group and stop receiving emails from it, send an email to angleproject+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Pasquale Granato]

Thanks Jamie.

Unfortunately your workaround did not work. There are still a lot of errors (even though the one I reported disappeared) . 

This brings me to the reason I'm building ANGLE in the first place. I'm trying to use a game engine called Oxygine on a Windows XP Embedded machine. 

I already have the required dependencies (namely libGLESv2.lib, libGLESv2.dll, libEGL.dll, d3dcompiler_47.dll, thanks again to Michel Braz de Morais) but probably from an old version of ANGLE. So if I run my project on the target machine (which is a WinXP Embedded) I get the error

The procedure entry point GetLogicalProcessorInformation could not be located in the dynamic link library KERNEL32.dll

which I get is related to ANGLE 

(It's the same error reported here https://bugs.chromium.org/p/chromium/issues/detail?id=573340 and probably is related to the same reason).

So my final question to you guys ANGLE's gurus is: does I have any chance to run an ANGLE backed app on a Windows XP Embedded machine?

Thanks again

Pasquale

[Jamie Madill]

I'm not entirely sure, sorry. We don't officially support Windows XP with ANGLE, since on that platform Chrome falls back to SwiftShader for software rendering.

[Brandon Thomas]

I was running into this error as well. Luckily the workaround you suggested seems to do the trick for me and takes care of the fatal errors related to not finding the vk header files. I'm building on Windows 10 w/ Visual Studio 2015.

I am however still running into a different Windows build issue that I haven't seen mentioned in these groups. This was brought up in the Issues on Microsoft's repo of Angle here https://github.com/Microsoft/angle/issues/120 
Basically the steps in the copy_compiler_dll.bat file that try's to copy d3dcompiler_47.dll always fails. Perhaps it is because I'm on Windows 10. As suggested in the issue, deleting the contents of that bat file does the trick. But I'm wondering if this is fixable so that there is no need for a workaround?

To unsubscribe from this group and stop receiving emails from it, send an email to angleproject...@googlegroups.com.

[Jamie Madill]

Interesting. Did you install the Windows 10 SDK before building ANGLE?

To unsubscribe from this group and stop receiving emails from it, send an email to angleproject+unsubscribe@googlegroups.com.

[Brandon Thomas]

I don't believe so. I just have Visual Studio Enterprise 2015 installed. So unless it got pulled in w/ something in its installer I just have the usual set of VS tools to build Visual C++ and Visual C#

[Jamie Madill]

Try installing the Windows 10 SDK as described in the docs:

https://chromium.googlesource.com/angle/angle/+/master/doc/DevSetup.md#required-tools

To unsubscribe from this group and stop receiving emails from it, send an email to angleproject+unsubscribe@googlegroups.com.

[Brandon Thomas]

That did the trick. I guess the part about "Not required to build" was incorrect. Seems like a required step now. Thanks for the help. 

[Jamie Madill]

Good point, I'll update the docs.

To unsubscribe from this group and stop receiving emails from it, send an email to angleproject+unsubscribe@googlegroups.com.

[Brandon Thomas]

I've run into an interesting problem now building everything from scratch. Again I only have Visual Studio 2015 and now the Windows 10 sdk.

When I first generated the Visual Studio solution/projects I only had VS2015, I did not have the Win10 SDK yet. So the projects it generated chose 8.1 as the Target Platform Version. I then installed the SDK after the fact, but didn't try regenerating the projects. Everything worked/compiled great. Even the copy_dll project worked.

Well I have since wiped out all that out and tried building again from scratch. Only now the projects gclient is generating choses 10.0.15063.0 as the Target Platform Version. And now when I try to build I get errors saying... TRK0005 Failed to locate: "rc.exe". The system cannot find the file specified.

I suspect my problem is that the Windows 10 SDK has some dependency on Visual Studio 2017, which I don't have. I tried to manually revert all the projects back to 8.1, but was getting some errors about now finding d3d11_3.h . 

Is there anything else I can do short of installing VS2017? Maybe there's a cmd line setting I can pass to the gclient tool.

[Jamie Madill]

Drat. That's the same problem as other users have. I haven't run into this myself. It likely is a problem with the Win10 SDK depending on something from VS2017. You can try installing 2017, the community edition is free.

To unsubscribe from this group and stop receiving emails from it, send an email to angleproject+unsubscribe@googlegroups.com.

[Brandon Thomas]

What version of the Windows 10 SDK do you have?

[Jamie Madill]

It looks like I have 14393.0 10586.0 on this machine, and it's currently configured to use 14393.0.

To unsubscribe from this group and stop receiving emails from it, send an email to angleproject+unsubscribe@googlegroups.com.

[Brandon Thomas]

After a bit of trial and error, I figured out that the 10.0.14393 Win SDK does indeed work for me too. The only work around I have to do is the "building of vulkan_layer_utils_static first" workaround mentioned above. The 10.0.15063 Win SDK seems to be specifically causing the error I mentioned before that we think indicates a new VS1017 dependancy. 

I was able to find that older Win 10 SDK here https://developer.microsoft.com/en-us/windows/downloads/sdk-archive 

I'm sure this info will quickly become outdated as I bet Angle will be moving to GN as well as VS2017, especially since it seems broken when building with the latest Win 10 SDK. But for the next little while, this is what I had to do to get everything building. 

[Jamie Madill]

OK thanks for reporting that Brandon. I just tried with gyp and VS2017, and had to tweak some things to get it working. The 15063 SDK that came installed with VS2017 didn't work for me out of the box, and I had to use the 14393 SDK. I'll see what the timetable is like for moving to GN.

To unsubscribe from this group and stop receiving emails from it, send an email to angleproject+unsubscribe@googlegroups.com.

[Jamie Madill]

It looks like the 15063 SDK has some significant changes, including removing the D3D9 support files. So we probably will have to support 14393 for the time being.

[Jamie Madill]

Actually, it seems if you reinstall the downloadable full SDK, D3D9 support is intact. I might have been seeing a problem with the version included by default in the VS2017 install.

I also updated the version of GYP included in ANGLE. If you update your ANGLE, install VS2017 and the standalone SDK, and do a fresh generate and build, you might have more success.