This used to be the repo providing the code for the version of VcXsrv that got shipped
with the Windows client of x2go (https://www.x2go.org). Starting with version 4.1.2.0
of the client (released 2018-06-25) VcXsrv's (then current) upstream version 1.20.0.0
is shipped. So this repo is no longer updated. Bug reports regarding the X server should
be opened at the upstream VcXsrv site: https://sourceforge.net/projects/vcxsrv/
VcXsrv Windows X Server (Custom builds by X2Go & Arctica)
The X2Go Project and Arctica Project are maintaining 1.15.2.x & 1.17.0.0-x branches of VcXsrv.
VcXsrv is a Windows X-server based on the xorg git sources (like xming or cygwin's xwin), but compiled with Visual Studio.
The upstream VcXsrv project can be found on SourceForge. Their last release of VcXsrv 1.15.2.x was 1.15.2.0, and it lacks Windows XP support.
Differences from VcXsrv
The primary differences from upstream VcXsrv are:
- Compatibility with Windows XP
- Prompt security updates
There are frequent security updates because numerous 3rd-party components are in the source tree. In addition to xorg-server, there are components such as openssl, freetype2 & various X11 libraries.
Other changes are:
- Only 32-bit builds (for the time being)
- Fixes for issues when used with nx-libs
- Improvements for contributors: Build Instructions are current & correct, we accept pull requests/patches, we respond to issues (although we cannot guarantee timely fixes), etc
- Better compression within the installer (for 1.17.0.0-x)
Download Builds:
Current versions of both 1.15.2.x & 1.17.0.0-x and be found on the Releases page on GitHub.:
1.15.2.6 and earlier, as well as 1.17.0.0-1, can be found here.
Community Support
You can post issues using GitHub.
You can also ask questions about VcXsrv usage or discuss development on the X2Go mailing lists. Note that this may change in the future.
Professional Support
Professional Support is available from one of the X2Go Developers.
Info for Developers
Why this repo and these builds exist.
You might be wondering why this repo and these builds exist. Why not upstream your changes?
- The primary developer of this repo and these builds (Mike DePaulo) tried multiple times to submit merge requests (the SourceForge equivalent of pull requests) and bug reports to the upstream VcXsrv project. The upstream VcXsrv developer (marha) only replied once. He rejected the merge request (for a legit reason), and gave good advice. However, he did not reject the merge request via the actual SourceForge system, and he has not responded since.
- SourceForge's support for git is terrible. For example, whenever I tried to merge request from branch Y on my personal repo to the master branch on the upstream VcXsrv repo, it tried to merge my master branch instead.
- SourceForge has recently done terrible things as GitHub has gained popularity
- Using a GitHub repo is much preferable to using a personal SourceForge repo in terms of visibility.
Explanation of Branches:
- master - The upstream VcXsrv branch that upstream VcXsrv is built from. Currently on the 1.16.x version series.
- release/1.15.2.x - the 1.15.2.x branch maintained by Arctica and X2Go.
- release/1.17.0.0-x - the 1.17.0.0-x branch maintained by Arctica and X2Go.
- release/external - Upstream copies the released (or git) versions of the various packages into this branch, which they call
released. They then update the packages.txt file at the root. This branch contains 0 modifications to those packages. Upstream then uses git's merge feature to merge these packages updates/upgrades into master, where upstream does make modifications to those packages. - release/external-1.15.2.x - same as
release/external, but forrelease/1.15.2.xrather thanmaster. - release/external-1.17.0.0-x - same as
release/external, but forrelease/1.17.0.0-xrather thanmaster.