pkg-config support was added very recently to gmp, so a lot of platforms
we want to support won't find gmp this way.

It is a (weird) dependency of nettle, and not part of nettle itself. So
split it to a separate module for clarity.

This is the standard method of finding it on Unix systems, so make sure
we use it. Still keep a fallback, though, for other systems, e.g.
Windows.

This is the standard method of finding it on Unix systems, so make sure
we use it. Still keep a fallback, though, for other systems, e.g.
Windows.

This is the current upstream so let's make use of it to get the latest
in features and fixes.

Newer CMake complains when you try to get the property of something
that isn't a target so use the specific if operator instead.

It's not supported in newer CMake, so try to deduce the library
filename from the target name.

This makes sure other build systems trigger properly, e.g. when
building Xvnc.

This is needed in order to get libtool to treat them as normal
libraries and not "convenience libraries". The latter are linked
with --whole-archive, which pulls a lot of unnecessary stuff into
Xvnc and libvnc.so.

This happens sometimes in order to enforce a strict ordering.

Otherwise you'll just get the initial response back every time
you call it.

We don't use that directory anymore.

GnuTLS can have different crypto backends, and it is rarely gcrypt
these days. So we should not be including that unconditionally,
and should not be pointing people at it either. Also remove the
section about Win32 binaries as those are out of date and probably
insecure. Lastly remove the section about static builds as it is
a general issue and in no way complete with just the GnuTLS portions.

git-svn-id: svn://svn.code.sf.net/p/tigervnc/code/trunk@5160 3789f03b-4d11-0410-bbf8-ca57d06f2519

git-svn-id: svn://svn.code.sf.net/p/tigervnc/code/trunk@5088 3789f03b-4d11-0410-bbf8-ca57d06f2519

git-svn-id: svn://svn.code.sf.net/p/tigervnc/code/trunk@4614 3789f03b-4d11-0410-bbf8-ca57d06f2519

git-svn-id: svn://svn.code.sf.net/p/tigervnc/code/trunk@4512 3789f03b-4d11-0410-bbf8-ca57d06f2519

git-svn-id: svn://svn.code.sf.net/p/tigervnc/code/trunk@4511 3789f03b-4d11-0410-bbf8-ca57d06f2519

git-svn-id: svn://svn.code.sf.net/p/tigervnc/code/trunk@4510 3789f03b-4d11-0410-bbf8-ca57d06f2519

git-svn-id: svn://svn.code.sf.net/p/tigervnc/code/trunk@4487 3789f03b-4d11-0410-bbf8-ca57d06f2519

- Added custom commands to create .libs and symlink to 
  static library so that autotools can actually find the 
  library in expected place.



git-svn-id: svn://svn.code.sf.net/p/tigervnc/code/trunk@4484 3789f03b-4d11-0410-bbf8-ca57d06f2519

network and Xregion, which a cmake build will NOT produce, this macro 
tries to create a libtool control file *.la for the specified target 
with libdependencies for a static library target.

Due to the automake part of Xvnc references to libtool files in source
tree you need to build vncviewer using cmake in the source tree.



git-svn-id: svn://svn.code.sf.net/p/tigervnc/code/trunk@4482 3789f03b-4d11-0410-bbf8-ca57d06f2519

take care of finding the gettext tools, not the headers and libraries needed
to build things. Use the licq project as inspiration on how to solve this.


git-svn-id: svn://svn.code.sf.net/p/tigervnc/code/trunk@4389 3789f03b-4d11-0410-bbf8-ca57d06f2519