buildscripts | Build scripts for generating official binaries

Recommended distro: Red Hat or CentOS Enterprise Linux 6 64-bit. Install all software necessary to build a 32-bit and a 64-bit version of TurboVNC (both 32-bit and 64-bit libjpeg-turbo SDKs should be installed in their default locations. Refer to BUILDING.md for more information.). The libjpeg-turbo JNI JAR files should be installed under /opt/libjpeg-turbo-jni.
OS X/macOS 10.7 (Lion) 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 4.1.x or later (available at <https://developer.apple.com/downloads> — Apple ID required.) The build scripts need this in order to produce TurboVNC binaries that are backward compatible with OS X 10.7. The Xcode Command Line Tools should be installed. The libjpeg-turbo SDK 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. The directory containing the 64-bit Visual C++ compiler (e.g. c:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\bin\amd64) should be listed in the PATH environment variable. The directory containing the 64-bit Windows SDK libraries (e.g. C:\Program Files\Microsoft SDKs\Windows\v7.0\Lib\x64) should be listed in the LIB environment variable. The directories containing the Visual C++ and Windows SDK header files (e.g. c:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\include and C:\Program Files\Microsoft SDKs\Windows\v7.0\include) should be listed in the INCLUDE environment variable. The official TurboVNC binaries are generated using the Windows SDK for Windows 7 and .NET Framework 3.5 SP1 (<http://www.microsoft.com/en-us/download/details.aspx?id=3138>), which contains Visual C 10.0, but any reasonably modern version of Visual C and the Windows SDK should work. Install all other software necessary to build a 32-bit and a 64-bit version of TurboVNC (both 32-bit and 64-bit libjpeg-turbo SDKs for Visual C++ should be installed in their default locations. Refer to BUILDING.md for more information.).
(where branch/tag is, for instance, "2.0.x" and defaults to "master") will generate both a pristine source tarball and binaries for the platform on which the script is executed. These are placed under $HOME/src/vnc.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/vnc.nightly/latest to $HOME/src/vnc.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 buildvnc -e (assuming that $HOME/src is a shared directory.). Run buildvnc -h for usage information.