source: branches/0.6-stable/INSTALL

$Id: INSTALL 731 2008-12-15 19:03:04Z peter $
{{{
Copyright (C) 2006 Jari Häkkinen
Copyright (C) 2007 Jari Häkkinen, Peter Johansson
Copyright (C) 2008 Peter Johansson

This file is part of svndigest, http://dev.thep.lu.se/svndigest

svndigest is free software; you can redistribute it and/or modify it
under the terms of the GNU General Public License as published by the
Free Software Foundation; either version 2 of the License, or (at your
option) any later version.

svndigest is distributed in the hope that it will be useful, but
WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
General Public License for more details.

You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software
Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307,
USA.
}}}
----------------------------------------------------------------------

= Svndigest Installation Guide =

Svndigest is a tool to extract development information and statistics
from a subversion repository. Svndigest is written in C++ and extracts
repository history using the subversion API. The resulting report is 
written to a user specifiable directory in HTML format. 

== Requirements ==

 * Subversion development files, i.e., header files and program
   libraries, version 1.4 or later.

 * This item should not be an issue if item above is fulfilled; the
   Apache Portable Runtime (APR) should be available if the subversion
   API was successfully compiled. Subversion depends on APR and in
   consequence, the dependency is inherited by svndigest.

 * Gnuplot.

 * A standard C++ compliant compiler with one extension: svndigest
   must be compiled with a C++ compiler that supports 'long long'
   types - GCC does this. This requirement arises from the fact that
   one of the underlying libraries, APR, is using 'long long'. APR is
   written in C and the C standard allows 'long long'.
   Even though the source is compiled with the -pedantic flag (which
   should catch the non C++ standard 'long long') there is another
   flag to suppress 'long long' diagnostics, -Wno-long-long.

== Installing svndigest ==

Below you'll find the generic FSF install instructions. To compile
and install svndigest you can follow the usual autoconf path:

 * `./configure`

 * `make`

 * Optionally, `make check` to run test programs. Some test programs
   are not enabled by default and the disabled tests should only be
   run by developers.

 * `make install`

The `./configure` script accepts a few options of interest for
svndigest. You can provide `./configure` with APR and subversion API
location information with `--with-apr=DIR` and `--with-svn=DIR`,
respectively. `--enable-staticbin` will create a static
svndigest binary. (Actually as static as the underlying program
libraries allows it to be, i.e., some external libraries might not
have been created/installed in static versions.) 

If you grabbed the source from the subversion repository you need to
run `./bootstrap` to setup autoconf files (see README.developer).


== FSF generic install documentation ==

Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004 Free
Software Foundation, Inc.

This file is free documentation; the Free Software Foundation gives
unlimited permission to copy, distribute and modify it.

=== Basic Installation ===

These are generic installation instructions.

The `configure` shell script attempts to guess correct values for
various system-dependent variables used during compilation.  It uses
those values to create a `Makefile` in each directory of the package.
It may also create one or more `.h` files containing system-dependent
definitions.  Finally, it creates a shell script `config.status` that
you can run in the future to recreate the current configuration, and a
file `config.log` containing compiler output (useful mainly for
debugging `configure`).

It can also use an optional file (typically called `config.cache`
and enabled with `--cache-file=config.cache` or simply `-C`) that saves
the results of its tests to speed up reconfiguring.  (Caching is
disabled by default to prevent problems with accidental use of stale
cache files.)

If you need to do unusual things to compile the package, please try
to figure out how `configure` could check whether to do them, and mail
diffs or instructions to the address given in the `README` so they can
be considered for the next release.  If you are using the cache, and at
some point `config.cache` contains results you don't want to keep, you
may remove or edit it.

The file `configure.ac` (or `configure.in`) is used to create
`configure` by a program called `autoconf`.  You only need
`configure.ac` if you want to change it or regenerate `configure` using
a newer version of `autoconf`.

The simplest way to compile this package is:

   * `cd` to the directory containing the package's source code and type
     `./configure` to configure the package for your system.  If you're
     using `csh` on an old version of System V, you might need to type
     `sh ./configure` instead to prevent `csh` from trying to execute
     `configure` itself.

     Running `configure` takes awhile.  While running, it prints some
     messages telling which features it is checking for.

   * Type `make` to compile the package.

   * Optionally, type `make check` to run any self-tests that come with
     the package.

   * Type `make install` to install the programs and any data files and
     documentation.

   * You can remove the program binaries and object files from the
     source code directory by typing `make clean`.  To also remove the
     files that `configure` created (so you can compile the package for
     a different kind of computer), type `make distclean`.  There is
     also a `make maintainer-clean` target, but that is intended mainly
     for the package's developers.  If you use it, you may have to get
     all sorts of other programs in order to regenerate files that came
     with the distribution.

=== 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=c89 CFLAGS=-O2 LIBS=-lposix`

   *Note Defining Variables::, for more details.

=== Compiling For Multiple Architectures ===

You can compile the package for more than one kind of computer at the
same time, by placing the object files for each architecture in their
own directory.  To do this, you must use a version of `make` that
supports the `VPATH` variable, such as GNU `make`.  `cd` to the
directory where you want the object files and executables to go and run
the `configure` script.  `configure` automatically checks for the
source code in the directory that `configure` is in and in `..`.

If you have to use a `make` that does not support the `VPATH`
variable, you have to compile the package for one architecture at a
time in the source code directory.  After you have installed the
package for one architecture, use `make distclean` before reconfiguring
for another architecture.

=== 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=PREFIX`.

You can specify separate installation prefixes for
architecture-specific files and architecture-independent files.  If you
give `configure` the option `--exec-prefix=PREFIX`, the package will
use PREFIX 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=DIR` 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.

If the package supports it, you can cause programs to be installed
with an extra prefix or suffix on their names by giving `configure` the
option `--program-prefix=PREFIX` or `--program-suffix=SUFFIX`.

=== Optional Features ===

Some packages pay attention to `--enable-FEATURE` options to
`configure`, where FEATURE indicates an optional part of the package.
They may also pay attention to `--with-PACKAGE` options, where PACKAGE
is something like `gnu-as` or `x` (for the X Window System).  The
`README` should mention any `--enable-` and `--with-` options that the
package recognizes.

For packages that use the X Window System, `configure` can usually
find the X include and library files automatically, but if it doesn't,
you can use the `configure` options `--x-includes=DIR` and
`--x-libraries=DIR` to specify their locations.

=== Specifying the System Type ===

There may be some features `configure` cannot figure out automatically,
but needs to determine by the type of machine the package will run on.
Usually, assuming the package is built to be run on the _same_
architectures, `configure` can figure that out, but if it prints a
message saying it cannot guess the machine type, give it the
`--build=TYPE` option.  TYPE can either be a short name for the system
type, such as `sun4`, or a canonical name which has the form:

     CPU-COMPANY-SYSTEM

where SYSTEM can have one of these forms:

     OS KERNEL-OS

See the file `config.sub` for the possible values of each field.  If
`config.sub` isn't included in this package, then this package doesn't
need to know the machine type.

If you are _building_ compiler tools for cross-compiling, you should
use the `--target=TYPE` option to select the type of system they will
produce code for.

If you want to _use_ a cross compiler, that generates code for a
platform different from the build platform, you should specify the
"host" platform (i.e., that on which the generated programs will
eventually be run) with `--host=TYPE`.

=== Sharing Defaults ===

If you want to set default values for `configure` scripts to share, you
can create a site shell script called `config.site` that gives default
values for variables like `CC`, `cache_file`, and `prefix`.
`configure` looks for `PREFIX/share/config.site` if it exists, then
`PREFIX/etc/config.site` if it exists.  Or, you can set the
`CONFIG_SITE` environment variable to the location of the site script.
A warning: not all `configure` scripts look for a site script.

=== Defining Variables ===

Variables not defined in a site shell script can be set in the
environment passed to `configure`.  However, some packages may run
configure again during the build, and the customized values of these
variables may be lost.  In order to avoid this problem, you should set
them in the `configure` command line, using `VAR=value`.  For example:

     ./configure CC=/usr/local2/bin/gcc

will cause the specified gcc to be used as the C compiler (unless it is
overridden in the site shell script).

=== `configure` Invocation ===

`configure` recognizes the following options to control how it operates.

`--help`
`-h`
     Print a summary of the options to `configure`, and exit.

`--version`
`-V`
     Print the version of Autoconf used to generate the `configure`
     script, and exit.

`--cache-file=FILE`
     Enable the cache: use and save the results of the tests in FILE,
     traditionally `config.cache`.  FILE defaults to `/dev/null` to
     disable caching.

`--config-cache`
`-C`
     Alias for `--cache-file=config.cache`.

`--quiet`
`--silent`
`-q`
     Do not print messages saying which checks are being made.  To
     suppress all normal output, redirect it to `/dev/null` (any error
     messages will still be shown).

`--srcdir=DIR`
     Look for the package's source code in directory DIR.  Usually
     `configure` can determine that directory automatically.

`configure` also accepts some other, not widely useful, options.  Run
`configure --help` for more details.