-
-
Notifications
You must be signed in to change notification settings - Fork 80
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
std::experimental::filesystem is deprecated for recent MSVC versions causing compilation failures #343
Comments
…ctually shouldn't happen, but still) - let's use `std::filesystem` instead of `std::experimental::filesystem` - as MSVC complains otherwise.
Ok, let's hope this does the trick. |
Okay, so I just noticed that in the CMakeLists.txt for the examples, you also link |
Separate bug for that :-) |
IIANM. that's supposed to do nothing for when the fs library isn't separate. But I may be wrong. |
Yeah, compilation will still succeed, you'll just get an annoying warning from MSVC. |
…ctually shouldn't happen, but still) - let's use `std::filesystem` instead of `std::experimental::filesystem` - as MSVC complains otherwise.
So... I can close this? |
Yes. |
…ctually shouldn't happen, but still) - let's use `std::filesystem` instead of `std::experimental::filesystem` - as MSVC complains otherwise.
…ctually shouldn't happen, but still) - let's use `std::filesystem` instead of `std::experimental::filesystem` - as MSVC complains otherwise.
…ctually shouldn't happen, but still) - let's use `std::filesystem` instead of `std::experimental::filesystem` - as MSVC complains otherwise.
…ctually shouldn't happen, but still) - let's use `std::filesystem` instead of `std::experimental::filesystem` - as MSVC complains otherwise.
…ctually shouldn't happen, but still) - let's use `std::filesystem` instead of `std::experimental::filesystem` - as MSVC complains otherwise.
The
jitify
example program complains about std::experimental::filesystem being deprecated by Microsoft when using C++17 with VS2019. Assuming the__cplusplus
is correctly set in the build process, I believe it should suffice to have something like:The text was updated successfully, but these errors were encountered: