3.3.1 Building with autoconf/automake

1. Create configure script (if necessary) If your check-out of SVN repository or extracted tar-ball doesn't contain `configure' script run from your object directory autoreconf ../PATH-TO-UNPACKED-SOURCES e.g.

             $ cd /usr/src/avldb-build
             $ autoreconf ../avldb
   

2. Configuration From your object directory, run the shell script `configure' located at the top level of the source tree. In the scenario above, you'd type

             $ ../avldb/configure ARGS...
   

   If you want to install avldb library to /usr/lib and includes to /usr/include specify installation prefix with :

             $ ../avldb/configure --prefix=/usr
   

   Please note that even though you're building in a separate build directory, the compilation may need to create or modify files and directories in the source directory.

   It may also be useful to set the CC and CFLAGS variables in the environment when running `configure'. CC selects the C compiler that will be used, and CFLAGS sets optimization options for the compiler.

   The following list describes all of the available options for `configure':

   `–prefix=DIRECTORY' Install machine-independent data files in sub-directories of `DIRECTORY'. The default is to install in `/usr/local'.

   `–exec-prefix=DIRECTORY' Install the library and other machine-dependent files in sub-directories of `DIRECTORY'. The default is to the `–prefix' directory if that option is specified, or `/usr/local' otherwise.

   `–disable-shared' Don't build shared libraries even if it is possible. Not all systems support shared libraries; you need ELF support and (currently) the GNU linker.

3. Compilation To build the library and related programs, type `make'. This will produce a lot of output, some of which may look like errors from `make' but isn't. Look for error messages from `make' containing `***'. Those indicate that something is seriously wrong.

   If you want to run a parallel make, simply pass the `-j' option with an appropriate numeric parameter to `make'. You need a recent GNU `make' version, though.

   Basic test programs (located in tests sub-directory) are build as default. See chapter `Running tests' for more informations.

4. Installation To install the library and its header files, and the Info files of the manual, type `sudo make install' or run `make install' as root.