-
Notifications
You must be signed in to change notification settings - Fork 248
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to use the library within a C++17 project #25
Comments
Sounds like there's two issues here. The first is that it seems like The second is the bug that you link that seems to have been fixed in later versions. I've ironically had to add a workaround for function pointers for C++14 since behavior was broken in VS2019. This workaround can be leveraged to have I'd say feel free to submit a PR that conditionalizes the above on your MSVC version. If someone comes along with a later version of VS that's still broken, we'll have to bump the version numbers again, but I don't believe that there's any better option, unfortunately. |
As a work-around, downgrade the NuGet package Microsoft.Windows.ImplementationLibrary to 1.0.210803.1 |
- Add the WIL directory to the include path - Define __WI_LIBCPP_HAS_NO_IS_AGGREGATE in VC++ 2017 as WIL doesn't build as it is microsoft/wil#25 PiperOrigin-RevId: 526162487
There is several compilation errors when trying to use the library within a C++17 project (I use the NuGet package and have no problem with std versions <= 14).
My version of VS2017 is 15.9.2.
Reproduction steps:
Create an empty console application, install Nuget Microsoft.Windows.ImplementationLibrary v1.0.190430.13 and just update your main to include wil/resources.h :
Here are the error messages I get:
Some messages seem related to this compiler issue: c++ compiler bug with decltype functions that have noexcept.
The text was updated successfully, but these errors were encountered: