-
Notifications
You must be signed in to change notification settings - Fork 34
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
ci:cmake: use default GCC,Clang per OS #194
Conversation
Thanks; how can we make the CI go through? |
.github/workflows/ci_cmake.yml
Outdated
@@ -18,27 +18,27 @@ env: | |||
CTEST_NO_TESTS_ACTION: "error" | |||
CMAKE_BUILD_PARALLEL_LEVEL: 4 | |||
CTEST_PARALLEL_LEVEL: 0 | |||
CMAKE_INSTALL_PREFIX: ~/libs |
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.
In p4est we default the install to local
relative to the local directory. Would it make sense to align this?
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'm just trying to reduce the parameters sprinkled throughout the YaML. To the CI or real computer system, it doesn't much care where it's installed, as long as it's writable.
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 see, you mean "~/local". I made this so here too.
Wondering what's going on on Windows, if this is a regression or a CI feature. |
001b2d1
to
210f587
Compare
Windows needed to have the $HOME variable used as PowerShell doesn't expand "~" any more. |
per Carsten, simplify compiler fanout by using only default GCC or Clang.
Cool, trying this out! |
per Carsten, simplify compiler fanout by using only default GCC or Clang.