Windows development environment

Speedwave development on Windows executes natively using Git Bash alongside MSVC compilation toolchains. Once initialized, the standard make workflow operates identically to macOS development.

Toolchain configuration

From Git Bash, run the one-time setup. It needs administrator rights and elevates itself:
Terminal window
```
make setup-dev-windows
```
The script installs the toolchain through Chocolatey (Git, GNU Make, rustup, Node.js, CMake, LLVM, Ninja, gitleaks and the Visual Studio 2022 C++ Build Tools) plus the pinned Vulkan SDK used by the Whisper transcription build. It enables long paths in the registry and in the system Git configuration, writes ~/msvc-env.sh with the MSVC environment and CMAKE_GENERATOR=Ninja, and creates a gitignored desktop/src-tauri/.cargo/config.toml with a short cargo target-dir. Anything it could not install is listed at the end instead of stopping the run.
Open a new Git Bash window so the updated PATH and environment apply, then install the project dependencies and start the app:
Terminal window
```
cd ~/Projects/speedwave
make setup-dev
make dev
```

GNU Make 4.x must come first on PATH: a legacy GnuWin32 Make 3.81 fails to parse multiline recipe expansions. The Vulkan transcription build is sensitive to path length and leaves only nine characters for the cargo target directory, which is why the setup writes a short target-dir; you can point it elsewhere with your own short target-dir or CARGO_TARGET_DIR.

For general prerequisites and Makefile targets, see Development environment setup. For testing instructions on Windows, refer to the Testing and validation guide.