mix/gosentry
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Recommend MinGW Mesa variant in VirtualBox/RDP workaround

Browse Source 
Update the OpenGL workaround to suggest the mingw release of Mesa instead of
msvc, as it matches the MSYS2 GCC toolchain used to build GoSentry. Both
variants work at runtime, but mingw is the more consistent choice.

Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
This commit is contained in:
mixeme
2026-06-18 00:17:20 +03:00
parent 975829ed70
commit 89704b0470
1 changed files with 4 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+4 -3
View File
@@ -197,9 +197,10 @@ Known workaround:
1. Download a Windows Mesa build from 1. Download a Windows Mesa build from
[mesa-dist-win](https://github.com/pal1000/mesa-dist-win/releases). For a [mesa-dist-win](https://github.com/pal1000/mesa-dist-win/releases). For a
regular Windows x64 GoSentry build, use the archive named like regular Windows x64 GoSentry build, use the archive named like
`mesa3d-<version>-release-msvc.7z`, for example `mesa3d-<version>-release-mingw.7z`, for example
`mesa3d-26.1.1-release-msvc.7z`. The `devel`, `debug-info`, `tests`, and `mesa3d-26.1.1-release-mingw.7z`. This matches the MSYS2 GCC toolchain used
checksum files are not needed for this workaround. to build GoSentry. The `devel`, `debug-info`, `tests`, and checksum files
are not needed for this workaround.
2. Open the downloaded archive and use the `x64` build from it. 2. Open the downloaded archive and use the `x64` build from it.
3. Copy the Mesa OpenGL DLL files from `x64` into the same directory as the 3. Copy the Mesa OpenGL DLL files from `x64` into the same directory as the
GoSentry `.exe`, for example: GoSentry `.exe`, for example: