commit 2f1644

2026-07-19 10:54:42 Matt Hughes: -/-

0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9

`development/building pointcaster.md` ..
@@ 13,16 13,15 @@
	The Pointcaster AppImage can be built from the repository root like so:
	```sh
	docker build -t pointcaster-linux .
-	docker run --rm -it \
-	-v ./:/pointcaster:Z -w /pointcaster pointcaster-linux \
+	docker run --rm -it -v ./:/pointcaster:Z pointcaster-linux \
	./scripts/build-linux-release.sh
	```
-	The `docker run` command arguments ensure that the repository is mounted inside the container and set as the working directory.
+	The `-v` command argument ensures the repository is mounted inside the container.

	For a development shell, invoke `bash` or `fish`, where you can configure and build using `cmake`:
	```sh
	docker run --rm -it \
-	-v ./:/pointcaster:Z -w/pointcaster pointcaster-linux bash
+	-v ./:/pointcaster:Z pointcaster-linux bash
	```
	Then from inside:
	```sh
@@ 48,11 47,11 @@
	```
	To produce a Pointcaster release package:
	```
-	docker run -v ./:C:\pointcaster -w C:\pointcaster pointcaster-win .\scripts-build-windows-release.ps1
+	docker run -v ./:C:\pointcaster pointcaster-win .\scripts-build-windows-release.ps1
	```
	For a development shell:
	```
-	docker run -it -v ./:C:\pointcaster -w C:\pointcaster pointcaster-win powershell
+	docker run -it -v ./:C:\pointcaster pointcaster-win powershell
	```
	> [!TIP]
	> You might benefit from passing some docker args to fully utilise available resources, e.g.: