Builds on Linux use a containerised environment created using the [Dockerfile](https://github.com/eidetic-av/pointcaster/blob/qt/Dockerfile) in the root of the repository. This handles download and configuration of all dependencies. Either [Docker](https://docs.docker.com/engine/install/) or [Podman](https://podman.io/docs/installation) must be installed and configured on your system to proceed.
+
Builds on Linux use a containerised environment created using the [Dockerfile](https://github.com/eidetic-av/pointcaster/blob/qt/Dockerfile) in the root of the repository. This handles download and configuration of all dependencies. Either [Docker](https://docs.docker.com/engine/install/) or [Podman](https://podman.io/docs/installation) must be installed and configured on your system to proceed.
The Pointcaster AppImage can be built from the repository root like so:
```sh
@@ 34,23 34,14 @@
> The docker image is used as a base for a [Development Container](https://containers.dev/) in IDEs that support it. Visual Studio Code will automatically install extensions needed for C++, CMake and QML. See the [devcontainer.json](https://github.com/eidetic-av/pointcaster/blob/qt/.devcontainer/devcontainer.json).
## Windows
-
Official Windows builds use the [Docker](https://docs.docker.com/engine/install/) engine.
-
-
> [!NOTE]
-
> Because of the nature of Docker on Windows, this isn't so great to use for development.
Automated Windows builds use Docker to configure the build environment. This configures Visual Studio Build Tools along with third-party binary dependencies. This is the supported method for producing release builds for Windows, however if you are looking to develop Pointcaster or a Pointcaster plugin you'll most likely want to [configure your development environment manually]().
