-
Notifications
You must be signed in to change notification settings - Fork 191
set the cmake build to out-of-source #50
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
Conversation
I suggest we test both in tree and out of tree.
The out of tree can be the default to test various compilers, etc. But on each platform we should have at least one test for in tree builds to ensure they still work.
…On Sun, Dec 29, 2019, at 4:18 AM, Pierre de Buyl wrote:
Change the github workflow for the cmake build.
I open the PR to trigger the workflow for the branch. The manual
makefiles are not touched.
You can view, comment on, or merge this pull request online at:
#50
Commit Summary
* set the cmake build to out-of-source
File Changes
* *M* .github/workflows/main.yml
<https://github.com/fortran-lang/stdlib/pull/50/files#diff-0> (6)
Patch Links:
* https://github.com/fortran-lang/stdlib/pull/50.patch
* https://github.com/fortran-lang/stdlib/pull/50.diff
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#50?email_source=notifications&email_token=AAAFAWCPMLOTFWZ2WDKIZ5LQ3CBPVA5CNFSM4KA22DJKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IDDA6JQ>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAFAWDZGU22X5XMLDIZCG3Q3CBPVANCNFSM4KA22DJA>.
|
Out of curiosity, what is the motivation for maintaining in-tree builds? Out-of-source builds are easier to cleanup after, and don't risk clobbering WIP changes. If we truly want to support both then I suppose we should test in source builds too, but I don't see a strong case for insisting on supporting both. In addition, out-of-source builds are more likely to fail from a misconfigured build system than in-source builds are. I don't care that much about whether or not we want to support in source builds, but we don't want a combinatorial explosion of our build matrix if we can avoid it. |
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.
LGTM
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.
Small fix: Delete stale comment please.
.github/workflows/main.yml
Outdated
@@ -52,10 +52,10 @@ jobs: | |||
run: brew install gcc@${GCC_V} || brew upgrade gcc@${GCC_V} || true | |||
|
|||
- name: Configure with CMake | |||
run: cmake -Wdev -S . -B . # We should build out of source but loadtxt needs fixing | |||
run: cmake -Wdev -S . -B build # We should build out of source but loadtxt needs fixing |
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.
run: cmake -Wdev -S . -B build # We should build out of source but loadtxt needs fixing | |
run: cmake -Wdev -S . -B build |
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.
Actually, this comment should be deleted if the issue is fixed and being tested.
I removed the comment. I didn't see that one could accept "suggested commits" online and did it via the CLI. Regarding in-tree builds, I don't use them in my projects, I don't know how useful they are. I proposed the cmake patch because I tested the build on my computer with the "idiomatic"
Maybe we need test users, with different coding habits. |
It seems @certik is one such "test user" as he reported elsewhere that he typically does in-tree CMake builds... Given the goal of supporting Makefiles and CMake, I would advocate for in-source builds being "unsupported". Interested parties can still try to keep them working, but I don't want to explode our CI test matrix anymore than 3 oses and 3 versions of Fortran compilers, unless there is a really good reason. |
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.
LGTM
I don't think we should encourage in-source builds. :) |
This PR is ready to go in, so I am going to merge it. |
I submitted #55 for in-tree CI tests. |
Change the github workflow for the cmake build.
I open the PR to trigger the workflow for the branch. The manual makefiles are not touched.