-
Notifications
You must be signed in to change notification settings - Fork 258
Build with .NET binding fails: missing metahost.h #35
Comments
Hi @leeprtc , Thanks for using our SDK. Yes, we are aware of this problem and we are working to find a fix and also document the root cause. Apparently this happens because when you have 8.1 and 10 SDK CMAKE defaults to Windows 10 SDK, which doesn't build for the current .NET Binding. So, in order to mitigate that while we work on a fix you can: Keep in mind that this will surface again if you run again the build.cmd. Let us know if this doesn't fix your problem. Thanks a lot, Angelo Ribeiro. |
Changing to Windows 8.1 SDK fixed the errors. Thanks! |
- Workaround for Issue Azure#35
Fixed with commit 00ab31f. Metahost.h is available in several locations (and they're all the same for our purposes), e.g. on my dev box:
Metahost.h is NOT available in the Windows 10 SDK for whatever reason. If you're targeting this SDK, I think it is expected that you'll pull it from the NETFX SDK instead. What's weird is that the NETFX SDK include path IS part of the INCLUDE env var, and INCLUDE should be searched by VC build, but apparently that's not happening here. So the fix is to add %NETFXSDKDir%Include\um to the include directories in the dotnet and dotnet_static projects. The NETFXSDKDir environment variable is set in the VS Developer Command Prompt (and the MSBuild Command Prompt). |
I followed the directions in Getting Started document. But when I ran"build.cmd --enable-dotnet-binding", I'm getting errors. The reason is it cannot find metahost.h. This affects dotnet, dotnet_hl, dotnet_hl_static, and dotnet_static projects.
Looking through my system, metahost.h can be found in the NETFXSDK include directory. Checking the project properties for dotnet* projects, I don't see the NETFXSDK include directory being specified as an additional include directory.
Is there a bug in the generation of the dotnet* project files?
Thanks,
Peter.
The text was updated successfully, but these errors were encountered: