-
Notifications
You must be signed in to change notification settings - Fork 447
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
Switch to C++11 #4128
Switch to C++11 #4128
Conversation
Travis CI will not fail, but AppVeyor will |
And I'm afraid, you'll have to wait ~2 hours because currently Travis CI is not usable because of their new policies |
FYI AppVeyor did not fail. Not sure what to make of it, hoping that it could mean that BOINC could easily switch to C++11, but I somehow expect that you will teach me better. :) |
Because you changed only build instructions for linux. But if you include any C++11 instruction - AppVeyor will fail because Visual Studio 2010 has not C++11 support |
Why we still support vs2010? |
@talregev because this will not be true soon 😜 |
@AenBleidd That is great news! :) |
This is not needed anymore |
Great. \o/ With which commit did the upgrade to a new C++ standard version happen? |
This decision was made offline and no commit was required. But if you need some as a start point, then it could be this one: 180ea88 |
This PR is, for now, primary to check if travis would fail with C++11 and as basis for discussion. Related to #4126 (comment).