Thy-Auth Installation notes
===========================

Build requirements
------------------

In order to compile Thy-Auth from sources certain additional software
must be present on the build system, including a POSIX-compatible
shell (usually /bin/sh), a POSIX compliant C library, a compiler that
supports C99 (GCC is such a compiler), GNU make, and the PAM
libraries.

To use the software, one will need a recent (0.8.7 and later) version
of Thy.

How to compile Thy-Auth
-----------------------

Its really quite simple - its about the same difficulty as compiling
any GNU software.

Just `cd' to the directory containing the sources, and type
`./configure'.  This will try to collect as much information about the
build environment as is needed to successfully compile the package.
This step usually takes a while, so feel free to sit back and drink a
cup of tea.

When `configure' finished successfully, the package can be compiled by
issuing the `make' (or `gmake' on certain non-GNU systems) command.
This will build all the Authorisers.

To install them all to their proper place, issue the `make install'
command, as the final step of the installation stage.  For information
about using the Authoriser, see the thy-auth(7) manual page, and that
of the installed Authorisers.

To clean the source tree, run `make clean' - this is useful if one
wants to force a rebuild or make a whole-tree diff between the
original and a modified version of Thy-Auth.  To also clean the files
`configure' created, use the `make distclean' command.  If one wants
to build Thy-Auth for a different machine, or with different options,
this is the command to issue.

Compilers and Options
---------------------

Some systems require unusual options for compilation or linking that
the `configure' script does not know about.  Run `./configure --help'
for details on some of the pertinent environment variables.

You can give `configure' initial values for configuration parameters
by setting variables in the command line or in the environment.  Here
is an example:

      ./configure CC=gcc CFLAGS="-Wno-shadow -O2" LIBS=-lposix

Installation Names
------------------

By default, `make install' will install the package's files in
`/usr/local/bin', `/usr/local/man', etc.  You can specify an
installation prefix other than `/usr/local' by giving `configure' the
option `--prefix=PATH'.

You can specify separate installation prefixes for
architecture-specific files and architecture-independent files.  If
you give `configure' the option `--exec-prefix=PATH', the package will
use PATH as the prefix for installing programs and libraries.
Documentation and other data files will still use the regular prefix.

In addition, if you use an unusual directory layout you can give
options like `--bindir=PATH' to specify different values for
particular kinds of files.  Run `configure --help' for a list of the
directories you can set and what kinds of files go in them.
