|
Monado OpenXR Runtime
|
Note: checked with Msys2-202610322 on Windows 11 25H2.
Start Menu, select MSYS2 CLANG64 to open a console using the clang64 environmentall members) The manifest file is installed in C:\msys64\usr\openxr_monado.json. It can be made active by changing a Windows Registry Key (more information here), or more easily using xrpicker-gui.exe. It can also be set, temporarily, from within a shell before to run an OpenXR client:
Cmdtool, use: set XR_RUNTIME_JSON=C:\msys64\usr\openxr_monado.json,PowerShell, use: $env:XR_RUNTIME_JSON = "C:\msys64\usr\openxr_monado.json"The built targets are installed in C:\msys64\usr\bin, the needed dlls are in C:\msys64\clang64\bin. To run a target from a non-msys64 environment, those paths have to be added to the Windows PATH environment variable.
System Properties panel to permanently change the content of the user's or system's Path,Cmdtool, the PATH can be set, temporally, using: set PATH=C:\msys64\usr\bin;C:\msys64\clang64\bin;PATH%PowerShell, the PATH can be set, temporally, using: $env:PATH = "C:\msys64\usr\bin;C:\msys64\clang64\bin;" + $env:PATHCurrently (2026-06-04), the OpenXR clients and monado-service must be run from the same environment (due to the way the IPC pipe is currently created):
monado-service is run from a Windows console (Cmdtool or PowerShell) or from the File Manager, the OpenXR client must also be run from a Windows console or from the File Managermonado-service is run from a Mingw64 console, the OpenXR client must also be run from a Mingw64 console.To build Monado from a Gitlab Windows Shell Worker, some configurations are needed on the host (in addition to above installation instructions):
C:\msys64\usr\bin to the Path system envvarMSYSTEM=CLANG64 in the system envvars (this must be set prior to the execution of the shell worker, hence the use of a system-wide envvar)in the runner's config.toml, set: