Native MSVC build from a Developer Command Prompt / Developer PowerShell for
VS (so cl, CMake, and Ninja are on PATH), using the bundled presets.
See the build guide for shared concepts. To cross-compile the Windows client from Linux/WSL instead, see wsl.md.
- Visual Studio C++ build tools (CMake + Ninja).
- The .NET 10 SDK.
- vcpkg, with
VCPKG_ROOTset to its installation directory. The presets selectx64-windowsorx86-windowsand chainload the repository architecture toolchain automatically.
$env:VCPKG_ROOT = "C:\vcpkg"# Configure (pick one)
cmake --preset windows-x64 # 64-bit player build
cmake --preset windows-x64-mueditor # 64-bit + editor + control socket
cmake --preset windows-x86 # 32-bit player build
cmake --preset windows-x86-mueditor # 32-bit + editor + control socket
# Build (pick the matching Debug/Release build preset)
cmake --build --preset windows-x64-mueditor-debug
cmake --build --preset windows-x64-mueditor-releaseThe configure presets are listed in CMakePresets.json; each has
-debug/-release build presets. The plain presets are the player
configuration (ENABLE_EDITOR=OFF, ENABLE_CONTROL_SOCKET=OFF); the
-mueditor presets are the developer configuration with both on. The
developer control socket (docs/control-socket.md) is only ever compiled
when ENABLE_CONTROL_SOCKET=ON; add -DENABLE_CONTROL_SOCKET=ON to a plain
preset to get it without the editor.
cd out/build/windows-x64-mueditor/src/Debug
.\Main.exeRun from the build output's src/<config> directory so the client finds its
assets, config.ini, and MUnique.Client.Library.dll (all placed there by the
post-build step).