Build cpp solvers as part of run

[fsimonis]

The elastic-tube-1d cpp solvers require to be build inside build directories.
In-source builds don't work:

cd elastic-tube-1d/solid-cpp
cmake .
cmake --build .
./run.sh
Cannot find ./build/SolidSolver

This PR changes the run script to automatically configure and (re)build the solver.

@MakisH is this compatible with the VM?

[MakisH]

We would/should indeed need to remove the pre-building in the provisioning of the vm, here: https://github.com/precice/vm/blob/a37b13a50ade7658e63bd17bbe3230df085bba7f/provisioning/install-precice.sh#L43-L46

I understand the problem, but I am not sure I understand the motivation for adding the building inside the run.sh. Is this to ensure that the user does it correctly?

Seamless automation is better than documentation, so I agree with this change, as long as it works fine with running the run.sh again and again (without calling clean.sh), and as long as the output remains short and clear in that case.

I have not tested this, but it looks straight-forward. Remember to update the VM and the documentation.

[fsimonis]

@MakisH This change also means that you don't have to explicitly build as part of the vm provisioning any more.

[MakisH]

@MakisH This change also means that you don't have to explicitly build as part of the vm provisioning any more.

But we still should remove that explicit building step:

We would/should indeed need to remove the pre-building in the provisioning of the vm, here: https://github.com/precice/vm/blob/a37b13a50ade7658e63bd17bbe3230df085bba7f/provisioning/install-precice.sh#L43-L46

[fsimonis]

But we still should remove that explicit building step:

@MakisH sorry, I somehow missed that part of your comment 😅

I understand the problem, but I am not sure I understand the motivation for adding the building inside the run.sh. Is this to ensure that the user does it correctly?

The problem is that our run script assumes an existing built solver in the build directory. As an example, calling cmake . && make in the solid-cpp dir doesn't work. So we either need to document this, extend run.sh to check more guesses, add a build.sh script, or build it directly in the run.sh.

Building it in the run script seemed the easiest to use from a user-perspective. Just ./run.sh to run.