Skip to content
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

appveyor.yml: Compile and test with latest version for __cplusplus macro on MSVC #1810

Closed
wants to merge 1 commit into from

Conversation

t-b
Copy link
Contributor

@t-b t-b commented Oct 23, 2019

According to 1 the C++ macro __cplusplus has always the value 199711L
even if you enable later version of C++ support via /std.

Use one job with /Zc:__cplusplus defined so that we know that it
compiles.

Close #1695.

@coveralls
Copy link

coveralls commented Oct 23, 2019

Coverage Status

Coverage remained the same at 100.0% when pulling 5e07fdf on t-b:add-zc-flag-for-msvc into 0db1692 on nlohmann:develop.

Copy link
Owner

@nlohmann nlohmann left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

After merging #1780, there are conflicts to resolve.

…cro on MSVC

According to [1] the C++ macro __cplusplus has always the value 199711L
even if you enable later version of C++ support via /std.

Use one job with /Zc:__cplusplus defined so that we know that it
compiles.

[1]: https://docs.microsoft.com/en-us/cpp/build/reference/zc-cplusplus?view=vs-2019
@t-b
Copy link
Contributor Author

t-b commented Nov 2, 2019

@nlohmann Done.

Copy link
Owner

@nlohmann nlohmann left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you check why an AppVeyor check failed?

@t-b
Copy link
Contributor Author

t-b commented Nov 7, 2019

@nlohmann See #1695 (comment) for a minimal example showing the problem. I'll will not find the time to fix that soonish.

@stale
Copy link

stale bot commented Dec 7, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the state: stale the issue has not been updated in a while and will be closed automatically soon unless it is updated label Dec 7, 2019
@t-b t-b closed this Dec 11, 2019
@nlohmann nlohmann added this to the Release 3.7.4 milestone Apr 10, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
platform: visual studio related to MSVC release item: 🔨 further change state: stale the issue has not been updated in a while and will be closed automatically soon unless it is updated
Projects
None yet
Development

Successfully merging this pull request may close these issues.

/Zc:__cplusplus leads to C2416
3 participants