Alexander Jaust
Alexander Jaust
The action currently fails as the bindings do not find the preCICE headers. I am not sure whether I should fix it by setting the `CPATH` as this action currently...
Just as an addition: It seems that the compilation and installation could be fixed easily by using `pkg-config` (see #135). It is still unclear how to make the installed preCICE...
Is the clean directive of the action a problem? See the docs of the action https://github.com/actions/checkout I added the `git log -n 5` command and a `ls -l` command to...
I missed some option in my action so hidden files/directories were **not** shown. I fixed that and I see some hidden files now: https://github.com/ajaust/python-bindings/runs/3966490670?check_suite_focus=true In fact, the `.git` is missing....
The checkout stage of the action might give us the answer: ``` The repository will be downloaded using the GitHub REST API To create a local Git repository instead, add...
By force installing a newer Git version, as suggested in https://github.com/actions/checkout/issues/335, it works. See: https://github.com/ajaust/python-bindings/runs/3966791087?check_suite_focus=true However only the git commit hash is visible, but not the version number. Could this...
[Fetching all history for all tags and branchesetch-all-history-for-all-tags-and-branches](https://github.com/actions/checkout#fetch-all-history-for-all-tags-and-branches) gives me a nonzero version number, but it prints ``` Installed version of bindings is v2.0.1.1+151.g56f7d14 ``` instead of `v2.3.0.1+somthing`. The commit...
Yes, we can close it, but we should not forget it. :smile:
I just found this issue now. I would mostly agree with with @fsimonis and if necessary, I would prefer the approach of @BenjaminRodenberg with `precice_noop`. At the moment I would...
@BenjaminRodenberg Is this an installation procedure we missed? I normally install all (preCICE + bindings) from source. I do this either by hand or via Spack and never ran into...