Build error in Windows Implementation library resource.h
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- cpp
- Domain
- build-system, operating-systems
Research direction
Start with the WebView2GettingStarted Win32 build and inspect packages/microsoft.windows.implementationlibrary.1.0.210930.1/include/wil/resource.h around line 2543. Reproduce with VS2017 15.9.39, Windows SDK 10.0.17763.0, and platform toolset v141, then determine whether the failure is specific to that toolchain or package version; done means the sample builds successfully or the compatibility requirement is documented.
Written by the indexing model from the issue text.
Description
Hi,
I'm getting the following build error when trying to build WebView2GettingStarted (Win32):
1>HelloWebView.cpp
1>c:\projects\webview2samples-master\gettingstartedguides\win32_gettingstarted\packages\microsoft.windows.implementationlibrary.1.0.210930.1\include\wil\resource.h(2543): error C2440: 'specialization': cannot convert from 'void (__cdecl *)(HANDLE) noexcept' to 'unknown-type'
1>c:\projects\webview2samples-master\gettingstartedguides\win32_gettingstarted\packages\microsoft.windows.implementationlibrary.1.0.210930.1\include\wil\resource.h(2543): note: Context does not allow for disambiguation of overloaded function
I'm using VS2017 15.9.39
Windows SDK version 10.0.17763.0
Platform Toolset v141 (I changed it from v142 for VS2017).
Release/x64
I installed the latest versions of WIL and WebView2 using the NuGet package manager.
Is there something else missing in order to build on VS2017?
- Dominant language
- C++
- Stars
- 1k
- Forks
- 520
- Avg merge
- 13m
- Merged PRs (30d)
- 1
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from MicrosoftEdge/WebView2Samples
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 72/100
MicrosoftEdge/WebView2Samples#5 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 10/100
MicrosoftEdge/WebView2Samples#282 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
MicrosoftEdge/WebView2Samples#277 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
MicrosoftEdge/WebView2Samples#273 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
MicrosoftEdge/WebView2Samples#268 ·
All issues in MicrosoftEdge/WebView2Samples
Similar issues
-
upstream update
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
conan-io/conan-center-index#31098 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
ml-explore/mlx-c#136 ·
-
bug chart-audit
Difficulty 1/5 Under an hour Newbie friendliness 92/100
Maintainers usually reply within 1 day