Installation notes for LibGII
-----------------------------

LibGII uses autoconf for configuration purposes, thus make sure you also
read the file INSTALL.autoconf.

Libraries and Includes:

If you have installed X in a nonstandard location, and the files do not get
found, use:

  --x-includes=DIR        X include files are in DIR
  --x-libraries=DIR       X library files are in DIR
  --with-x                use the X Window System

Other missing libraries/includes (separated by colons) can be added with:

  --with-extra-includes=DIR
                          add extra include paths
  --with-extra-libs=DIR   add extra library paths
where DIR is a colon separated list of directories.

In case you are toying with the thought to build LibGGI statically for some
reason, please note, that due to the dynamic nature of LibGGI this makes no 
sense and is unsupported, so don't use:

  --enable-static         not supported

LibGII stores its configuration in /etc/ggi by default, as some possible
companion libraries (like SVGAlib and DGA) require root permissions.
As the conffile contains library name mappings, it has to be protected
against tampering. However for testing purposes, you might want to install
LibGII in your own user home or something. Thus you can set the prefix
with:

  --enable-confdir=NAME   specify the directory where to put libgii.conf
                          [default=/etc/ggi]

Some targets/inputs require proper locking for threadsafety. You can choose 
a suitable kind of locking for your machine using:

  --enable-mutexes=TYPE   force the kind of mutexes to use
                            (pthread, dynpthread or int)

Pthread is plain usage of libpthread. Note, that this triggers a weird bug
in glibc on Linux, and you are advised to use the dynpthread option there,
which ensures that real pthread mutextes are used instead of the empty stubs
contained in the libc. If you have no libpthread or if it is broken, choose
int. But that's only a "last resort". It's _not_ safe.

In case you are never ever interested in debugging LibGGI, you can compile
out all debugging code, making it a bit smaller and faster:

  --disable-debug         don't build with run-time debugging (speed freaks)

If you are the opposite type, and want to help plug memory holes, you might
want to use:

  --enable-memdebug       include memory usage debugging code in LibGG

In case you do not want some input libraries to be built, or want to force
experimental or wrongly undetected inputlibs to be build, you can use:

  --disable-filter-mouse  don't build the mouse filterlib
  --disable-filter-save   don't build the save filterlib
  --disable-null          don't build the null inputlib (discouraged - this
                            is REQUIRED by LibGGI)
  --disable-stdin         don't build the stdin inputlib
  --disable-x             don't build the x inputlib
  --disable-xwin          don't build the xwin inputlib
  --disable-mouse         don't build the mouse inputlib
  --disable-linux-mouse   don't build the linux-mouse inputlib
  --disable-linux-kbd     don't build the linux-kbd inputlib
  --disable-linux-joy     don't build the linux-joy inputlib
  --disable-spaceorb      don't build the spaceorb inputlib
  --enable-pcjoy          build the pcjoy inputlib

