-
Notifications
You must be signed in to change notification settings - Fork 66
cmake: Use standard try_run
instead of execute_process
#126
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
cmake: Use standard try_run
instead of execute_process
#126
Conversation
Signed-off-by: Cristian Le <git@lecris.dev>
Signed-off-by: Cristian Le <git@lecris.dev>
Signed-off-by: Cristian Le <git@lecris.dev>
Signed-off-by: Cristian Le <git@lecris.dev>
Signed-off-by: Cristian Le <git@lecris.dev>
@prj- See this PR, this should address your issue in #123 (comment) |
I don't understand what is going here. When will |
The failure that you shared in #123 is unrelated to CMake 4.0. It should be occurring in the
|
It does not.
|
I've tried to cherry-pick 2f142d6 on top of |
Unless you can provide me with a dockerfile reproducer I cannot reproduce the issue you've had because
Philosophy, I do not want things merged without proper testing. The tests may not cover or all edge-cases, but I do not want to add PRs without making sure the changes do not have a regression, and the minimum for that w.r.t. CMake environments is #123. Locally I am still unable to build this from a vanilla Fedora container so I am reliant on the CI environment for test coverage. Otherwise I do organize my PRs and commits to make the review process as easy as possible for upstream developers. If you want to help, you can contact the upstream developers to get #123 and this PR merge in a timely manner. Or if you are opposed to my philosophy, go ahead and cheerry-pick the change and make another PR and accelerate the process there as you see fit. |
@langou, ScaLAPACK currently can't be configured with CMake 4.0.0. Do you have plans to fix this, e.g., by merging some of the open PRs? |
Hi @prj-, do you have a suggestion on which open PRs to merge? Julien. |
#123 and then this one |
Thanks @LecrisUT. Let me know if there are issues. Thanks a lot. |
The previous approach creates unwanted artifacts in the source directory and does not propagate generator/fortran compiler, etc.
Depends-on: #123