-
Notifications
You must be signed in to change notification settings - Fork 43
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
use C++17 #703
base: develop
Are you sure you want to change the base?
use C++17 #703
Conversation
9ce8a68
to
21262f0
Compare
21262f0
to
f9ef443
Compare
@nychiang can you please confirm |
CMakeLists.txt
Outdated
set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -std=c++17 -lstdc++fs ") | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am not sure if this is portable. It will probably not work with MSVC, for example.
Kitware suggests adding language standards to targets such as
target_compile_features(HIOP PRIVATE cxx_std_17)
My understanding is that the built-in target cxx_std_17
is supposed to add correct flags for the compiler of your selection.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I doubt it is going to be an issue, because ExaGO only links to HiOp.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
after checking others' code, e.g., RAJA, MFEM, etc..., I don't think I need to specify -std=c++17
or target_compile_features
. Just pushed another commit for review.
Set C++17 as the standard in CMake files