These scripts are used to build the "official" VirtualGL binaries, which work on any Linux platform with GLIBC 2.17 and later, as well as Windows XP and later and OS X/macOS 10.9 and later.

See BUILDING.md in the VirtualGL source for basic build requirements. Additional build requirements for these scripts are listed below.

Recommended distro: Red Hat or CentOS Enterprise Linux 7 x86-64

Complete Linux build environment requirements are best understood by examining the official Docker recipe at https://github.com/VirtualGL/docker.

macOS 10.15 (Catalina) or later required

CMake should be installed somewhere in the PATH. The version in MacPorts (http://www.MacPorts.org) works, or just install the CMake application from the DMG (http://www.cmake.org) and add /Applications/CMake.app/Contents/bin to the PATH.

Xcode 12.0 or later (available at https://developer.apple.com/downloads -- Apple ID required.)

XQuartz must be installed (XQuartz provides the X11 headers and link libraries.)

The libjpeg-turbo SDK (v2.1.x or later) should be installed in its default location.

Windows XP 64-bit or later required

CMake (the Windows native version, not the Cygwin version) should be installed somewhere in the PATH.

Install all other software necessary to build a 32-bit and a 64-bit version of VirtualGL-Utils. Refer to BUILDING-win.md for more information.

Executing

buildvgl [branch/tag]

(where branch/tag is, for instance, "2.4.x" and defaults to "main") will generate both a pristine source tarball and binaries for the platform on which the script is executed. These are placed under $HOME/src/vgl.nightly/YYYYMMDD/files, where YYYYMMDD is a build number based on today's date. If the build is successful, then a sym link will be created from $HOME/src/vgl.nightly/latest to $HOME/src/vgl.nightly/YYYYMMDD.

Once a full build is completed on one platform, then you can use the existing source tarball to build binaries on other platforms by running buildvgl -e (assuming that $HOME/src is a shared directory.)

NOTE: On Windows, buildvgl should be run from inside an MSYS shell. If you are mounting your home directory as a drive letter (e.g. H:), then set the HOME environment variable to the MinGW path for that drive (e.g. /h) prior to running buildvgl.

Run buildvgl -h for usage information.

To sign the RPMs and DEBs using a GPG key, create a file called gpgsign in the same directory as buildvgl, and include the following contents in the file:

GPG_KEY_NAME={full name of GPG key to use (as listed in 'gpg --list-keys')}
GPG_KEY_ID={key ID of GPG key to use (as listed in 'gpg --list-keys')}
GPG_KEY_PASS={password for GPG key}

debsigs must be installed and in the PATH.

To sign the Mac installer package and DMG, create a file called macsign under setupscripts/, and include the following contents in the file:

MACOS_APP_CERT_NAME={full name of Mac Developer ID Application certficate (in the macOS keychain) used to sign the DMG}
MACOS_INST_CERT_NAME={full name of Mac Developer ID Installer certificate (in the macOS keychain) used to sign the installer package}

OS X/macOS 10.11 "El Capitan" or later is required in order to sign the Mac package/DMG.

To sign the Windows installers using a code signing certificate, create a file called mssign in the same directory as buildvgl, and include the following contents in the file:

MS_KEY_FILE={full MinGW path to a .pfx file containing the code signing certificate}
MS_KEY_PASS={password for certificate}

signtool (available in the Windows SDK) must be in the PATH.