-
Notifications
You must be signed in to change notification settings - Fork 165
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
Remove C++11 build jobs from CI #696
Labels
test
New tests development or missing tests issues, no new functionality
Milestone
Comments
Shouldn't this be on the 1.81 milestone then?
Bold to assume that, I thought to get rid of all |
mloskot
added a commit
to mloskot/gil
that referenced
this issue
Jun 27, 2022
Why? If Boost.GIL 1.80 is said and set to require C++14 or later, then what is the reason to keep anything C++11? |
1 task
mloskot
added a commit
to mloskot/gil
that referenced
this issue
Jun 27, 2022
Follow-up to PR boostorg#677 and Issue boostorg#696
mloskot
added a commit
to mloskot/gil
that referenced
this issue
Jun 27, 2022
Follow-up to boostorg#677 Related to boostorg#696
1 task
mloskot
added a commit
that referenced
this issue
Jun 27, 2022
* build: test/Jamfile now check for cxx14_constepxr Closes #696
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
For Boost 1.80, we have announced the switch from C++11 to C++14 with Boost 1.80.
This should be followed with removal of C++11 builds from our CI-s.
Yes, GIL may still build as C++11 for a while after the release of Boost 1.80, but keeping those jobs will be confusing.
Removing them will also speed up our CI operations.
The text was updated successfully, but these errors were encountered: