Use statically linked Raylib and add docs on dev setup

.gitignore

···
+# Data
+/data/
+
+# Built files
 /build/
 
-/data.bak/
+# Backups
+*.bak
+
+# Raylib
+/raylib.tar.gz
+/raylib/

compile_flags.txt

···
 
 -std=c99
 -Iinclude/
+-Iraylib/src/
 -xc-header
 
 -DKF_SANITY_CHECKS

readme

···
 Develop
 -------
 
+  Libraries (Debian):
+    Raylib:
+      libasound2-dev libx11-dev libxrandr-dev libxi-dev libgl1-mesa-dev libglu1-mesa-dev libxcursor-dev libxinerama-dev libwayland-dev libxkbcommon-dev
+    Keraforge:
+      liblzma-dev
+
+  Initialise a development environment:
+  `sh run.sh init`
+
   Build "system" is contained in a folder of shell scripts,
 `scripts`. You can run these with the `run.sh` script to
 run multiple tasks in order. Generally:

scripts/_config.sh

···
 export KF_DEBUG_CFLAGS="-g -DKF_SANITY_CHECKS"
 export KF_DEBUG_LFLAGS="-g -rdynamic"
 
-export CFLAGS="-Wall -Wextra -Werror -std=c99 -Iinclude/ -c -DKF_GNU $KF_DEBUG_CFLAGS"
-export LFLAGS="-lraylib -lm -lGL -lpthread -ldl -lrt -lX11 -llzma $KF_DEBUG_LFLAGS"
+export CFLAGS="-Wall -Wextra -Werror -std=c99 -Iinclude/ -Iraylib/src/ -c -DKF_GNU $KF_DEBUG_CFLAGS"
+export LFLAGS="raylib/src/libraylib.a -lm -lGL -lpthread -ldl -lrt -lX11 -llzma $KF_DEBUG_LFLAGS"

scripts/init.sh

···
+#!/usr/bin/env sh
+
+set -e
+
+RAYLIB_VERSION=5.5
+
+if [ ! -e "raylib.tar.gz" ]
+then
+	curl -Lo raylib.tar.gz https://github.com/raysan5/raylib/archive/refs/tags/$RAYLIB_VERSION.tar.gz
+fi
+
+if [ ! -e "raylib/" ]
+then
+	tar -xkf raylib.tar.gz && mv -v raylib-$RAYLIB_VERSION raylib
+fi
+
+cd raylib/src
+make
+cd ../..
+