[ROS-O] No explicit requests for c++11 #292
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Ping @gavanderhoorn . 🎅 |
C++11 has been the default for compilers targeted in this branch. gtest requires c++14 since v1.13 (Jan 2023) and building the tests on newer systems fails.
v4hn
force-pushed
the
pr-no-explicit-11
branch
from
7bf9b92
to
bd45f15
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
C++11 has been the default for compilers targeted in this branch.
gtest requires c++14 since v1.13 (Jan 2023) and building the tests on newer systems fails.
If this is not endorsed by the authors, it's also possible to check for externally provided values for
CXX_STANDARDbefore setting it, but it's much more convenient to simply drop it and keep the codebase compiling without special triggers on modern systems.