I forgot that make check does not build the C examples which are our only way to test the C API. One has to try running make examples after having installed the software. This used to be checked in the Docker CI (and is thus still here in the Docker-based part of our CI) but I did not reproduce this behaviour in the newly introduced "APT-based" and "OPAM-based" CIs. This PR fixes that.
It is currently WIP as I suspect it might not work on Windows (we've had problems before). When the CI is fixed, I'll re-run the job and check that it indeed works on Windows (or fix it).
I forgot that
make check
does not build the C examples which are our only way to test the C API. One has to try runningmake examples
after having installed the software. This used to be checked in the Docker CI (and is thus still here in the Docker-based part of our CI) but I did not reproduce this behaviour in the newly introduced "APT-based" and "OPAM-based" CIs. This PR fixes that.It is currently WIP as I suspect it might not work on Windows (we've had problems before). When the CI is fixed, I'll re-run the job and check that it indeed works on Windows (or fix it).