Installation
************

Installing `GDL' version 1.2.0
==============================

To compile and install `GDL':

  1. Determine what Foundation library you have installed on your
     system.  This package was tested with NeXT's Foundation,
     libFoundation, and the GNUstep Base Library.

     The configure script will try to determine the Foundation libraries
     installed on your system, but if it's unable to determine the
     library or if you have more than one Foundation library installed;
     then you need to specify which Foundation library to use.

     To do this, you should set the FOUNDATION shell variable to the
     Foundation library name; this example selects the NeXT Foundation:
          FOUNDATION=foundation ./configure

     Use `gnustep-base' for the GNUstep Base Library and
     `libFoundation' for the libFoundation library.

  2. Determine if you need the FoundationExtensions library; the
     following scenarios require this library:

        * NEXTSTEP 3.3 and NeXT's Foundation library.

        * GNUstep Base Library on any platform.


  3. Determine which database adaptors to compile.  The header files and
     libraries for your database will be required in order to compile
     the source code for the adaptor.  If these header files and
     libraries are not in the standard include and library paths for
     GCC, then use the `CFLAGS' and `LDFLAGS' make variables to specify
     the directories.

     Pass the parameter `--with-sqlserver' to compile the Microsoft
     SQLServer database adaptor, `--with-postgres95' to compile the
     PostgreSQL database adaptor, and `--with-sybase' to compile the
     Sybase database adaptor.  The following example specifies that the
     PostgreSQL database adaptor be compiled:
          ./configure --with-postgres95

     Use -with-Oracle7 and/or -with-Oracle8 to compile the Oracle
     adaptors. Please refer to eoadaptors/Oracle[78]/INSTALL for
     additionnal information about compiling and installing these
     adaptors.

     Type `./configure --help' to list what other parameters
     `configure' accepts, and what other database adaptors can be
     compiled.

  4. Configure the package for your system.  In the directory that this
     file is in, type `./configure'.  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.

     If your system requires unusual options for compilation or linking
     that `configure' doesn't know about, you can give `configure'
     initial values for some variables by setting them in the
     environment.  In Bourne-compatible shells, you can do that on the
     command line like this:
          CC='gcc -traditional' DEFS=-D_POSIX_SOURCE ./configure

     If you need to do unusual things to compile the package, we
     encourage you to figure out how `configure' could check whether to
     do them, and mail diffs or instructions to the address given in
     the `README' so we can include them in the next release.

  5. Type `make' to compile the package; `GDL' requires that you use
     GNU make.  If you want, you can override the `make' variables
     `CFLAGS' and `LDFLAGS' like this:
          make CFLAGS=-O2 LDFLAGS=-s

  6. Type `make check' to run the tests.  The tests are written for a
     specific database adaptor; read the file `tests/README' regarding
     how to prepare your database.

     All the tests are written using the DejaGnu testing framework, so
     if you don't have it installed then you will need to do so before
     trying out these tests.

  7. Type `make install' to install programs, data files, and
     documentation.

  8. You can remove the program binaries and object files from the
     source directory by typing `make clean'.  To also remove the
     Makefile(s), and `config.status' (all the files that `configure'
     created), type `make distclean'.

     The file `configure.in' is used as a template to create
     `configure' by a program called `autoconf'.  You will only need it
     if you want to regenerate `configure' using a newer version of
     `autoconf'.


