libXft is needed to build FLTK for the RHEL 6 RPM.

The supporting scripts weren't really up to date, so remove them
and just require the packager to include FLTK in the source
tarball.

It is needed by x0vncserver.

It is needed to build Xvnc.

They include a new enough version, so stop doing our own build.

Patch originally by @KenMilmore on GitHub.

Packages for RHEL 5 and Ubuntu 12.04 are no longer maintained, so
remove those files.

These are for ancient versions of FLTK and are not needed in the
versions required by us.

The contributed script uses bash features extensively and does not work with ksh.

Two minor issues:

This script is written in python two which is depreciated, and should be rewritten in python three, but I have so far been successful in not learning python. :-) to simplify debugging I have clarified that it needs a python two interpreter.

This script downloads an old version of mesa (an update may be appropriate),  unfortunately the release candidate previously specified is no longer available, so an update to the next released version was made.

Modern fontconfig needs it, so make sure it is included.

Add basic templates for users to follow so that we get the information
we need directly in the initial report.

Add more checks and fix some callers to make sure that the server
core always has a valid screen layout configured.

Make the API consisitent by requiring the caller to check what the client
supports before calling any of the write* functions. This avoids the
confusion that the functions might not always do anything.

Avoid having the callers need to know about the different variants
of these functions and instead have the writer pick the most appropriate
extension.

This is what the protocol requires, rather than sending what the
client specified in the request. This should be the same in practice
except for failures and possibly some races.

32 bits are not enough to keep track of all the pixels that might
flow through the system. Expand things to 64 bits, which should cover
all reasonable uses.

There is a range of key codes that are never sent by a real keyboard
and are therefore used by layouts to hide "fake" mappings. Make sure
to only use these as a fallback as some applications get confused
when they see these codes.

Use cmake TIMESTAMP function

It now accepts this parameter, so make sure it is documented.

We disabled it in 0a0e582 since it didn't have support for resizing.
But it got that support in 242c5b2, yet we forgot to allow this
setting again.

We need to check earlier if we are going to send this refresh or
not. Otherwise we send out pings pointlessly, and we also stall
the request loop with a client as we clear the requested region
without actually sending an update message.

It makes the logic a bit easier to follow, and also fixes the
case where just a fake update is needed.

Fallout from beb59a43.

We need a larger range to handle the temporary overflow caused by
the Floyd-Steinberg dithering.

The debug builds do extra check, so chose that mode for Travis so we
get early warnings for problems.

because it is not only platform independent
but also allows to override the build date
This helps to make tigervnc builds reproducible

See https://reproducible-builds.org/ for why this is good

Also adds UTC flag, to be independent of timezone.
Also changes JAVA_DATE format to ISO-8601 date format.

Requires cmake-2.8.11+ from 2013

Logging revealed that a few empty damage regions are emitted on startup. Those don't need to be rendered to the Surface pixmap.

The Pixmap is filled in as updates from the server arrive. Before the first full update, it would contain undefined contents, which would be rendered onto the ViewPort.
Clearing the Pixmap is only done on startup and when changing the server resolution, so it's not performance critical.

It doesn't belong on each socket server object as timers are global.
Force implementations to call the Timer system directly instead,
avoiding any middle men.

Get this timeout in to the timer system as well to make things
simpler and more robust.

Do a proper cleanup when one of the termination timeouts trigger
rather than just exiting on the spot. This makes sure we don't leave
stray stuff around, e.g. unix socket files.