Now ITEA should work with both github actions and your HPC. It is not the best approach, but given the problem Haskell stack has with using the conda env paths, this should do.
What I have done:
generated a binary of ITEA built into a CentOS 7 image (thanks @foolnotion)
commited into ITEA repo the binary file, a modified python wrapper and a script that sets some env variables before running ITEA (so that it can use the libs installed in conda env)
commited a copy of libgsl.so.0 (it would be best to copy from the conda env path, but I don't have access to this path until after the CI is done running)
included the required libs in environment.yml
include a conda init bash into configure.sh
Check if that's ok, I had to add this conda init so that the conda activate works inside CI and so I can use the $CONDA_PREFIX variable.
Now ITEA should work with both github actions and your HPC. It is not the best approach, but given the problem Haskell stack has with using the conda env paths, this should do. What I have done:
environment.yml
conda init bash
intoconfigure.sh
Check if that's ok, I had to add this conda init so that the
conda activate
works inside CI and so I can use the $CONDA_PREFIX variable.