Automated Windows builds use [Docker](https://docs.docker.com/engine/install/) to configure the build environment. [`scripts/windows.Dockerfile`](https://github.com/eidetic-av/pointcaster) installs Visual Studio Build Tools along with third-party binary dependencies in an isolated Windows container. This is how release builds are produced, but if you are looking to develop Pointcaster or a Pointcaster plugin you'll most likely want to build and debug using an IDE - in which case you'll need to [configure dependencies manually](#windows-builds-in-an-ide).
+
Automated Windows builds use [Docker](https://docs.docker.com/engine/install/) to configure the build environment. [`scripts/windows.Dockerfile`](https://github.com/eidetic-av/pointcaster/blob/qt/scripts/windows.Dockerfile) installs Visual Studio Build Tools and other binary dependencies in a Windows container. This is how release builds are produced, but if you are looking to develop Pointcaster or a Pointcaster plugin you'll most likely want to build and debug using an IDE - in which case you'll need to [configure dependencies manually](#windows-builds-in-an-ide). You can use [Docker Desktop](https://docs.docker.com/desktop/setup/install/windows-install/) to build and run Pointcaster on Windows and edit source code in whatever editor you want, but you're on your own figuring out how to Debug in this workflow.
-
Building using the Docker image
+
The following commands assume you have a working docker installation capable of running Windows containers on the command line.
