Add building and container recipes

[D4rkDuck]

Gitlab Username: luxik
Instructions to run the project can be found in the readme, but I will include it here aswell:

Instructions

The imageName has to be chosen! ("cmakeFight" could be a fitting name)

1. Build the image via (getting all dependencies will take some time)

docker buildx build -t <imageName> .

2. Run the container

docker run -it --mount type=bind,src=.,dst=/mnt/host/cmake-exercise <imageName>

3. Change directory into the repo

cd cmake-exercise

4. Run the shell script (build folder should not exist beforehand!)

./build_and_run.sh

Expected output:

Let's fight with CMake, Docker, and some dependencies!

Solve Poisson problem with FEM using deal.II
FEM results available in `solution.vtk`. Try visualizing with Paraview.

Modify a flat set using boost container
Elements in s1: 1       2       3       4

Inspect the current directory using boost filesystem
"." is a directory containing:
    "CMakeCache.txt"
    "CMakeFiles"
    "Makefile"
    "cmake_install.cmake"
    "main"
    "solution.vtk"

Parse some yaml file with yaml-cpp
  ../yamlParser/config.yml
Version: 1.2.3

[MakisH]

Everything looks mostly good here and works, thanks! Just some minor comments, which are not affecting functionality in this case, but would be something to note for next projects.

[MakisH]

While uppercase/lowercase does not matter, I would stick to one (typically uppercase in Dockerfiles). Similarly for CMake (lowercase).

[MakisH]

This leads to the = being part of the value:

root@22cc76132608:/mnt/host# echo $LD_LIBRARY_PATH 
= /usr/local/bin

Use either ENV var=value or the legacy ENV var value.

By the way, the value should be /usr/local/lib, since it is a library.

[MakisH]

FYI, this can also be different from the name of the executable (and is typically something more descriptive).

[MakisH]

The WORKDIR paths should be absolute, but this worked.