Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002 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').

The simplest way to compile the GscApi package is:

  1. Create a directory called `buildGsc' in the same directory in which
     the GscApi tarball was extracted. For example, if the tarball was
     extracted to /home/user, the tarball contents will be located in
     the directory /home/user/GscApi-x.y.z, where x.y.z is the version of
     GscApi packaged in the tarball. This version matches the version embedded
     in the name of the tarball. After this step is completed, the
     directory /home/user/buildGsc should exist.

  2. `cd' to the directory created in step 1 and type `../GscApi-x.y.z/configure'
     to configure the GscApi package for your system.  If you're using `csh'
     on an old version of System V, you might need to type
     `sh ../GscApi-x.y.z/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.

  3. Type `make' to compile the GscApi package.

  4. Type `make install' to install the API libraries, header files,
     documentation and sample code.

  5. You can remove the program binaries and object files from the
     source code directory by typing `make clean'. You can uninstall the
     GscApi package by typing `make uninstall'

  6. To build applications that use the GscApi libraries, the linux dynamic
     linker must be able to find them. In order for the linker to be able
     to find them, the necessary links must be present. To do this, firstly the
     path to the GscApi libraries must be added to the file /etc/ld.so.conf.
     This can be done with a text editor. Open the file with a text editor and
     add the following line:

	/usr/local/lib

     Once the file has been edited, type the command `ldconfig' from a shell
     prompt to update the links.

  7. The last step to configure the system to build applications using the
     GscApi libraries is to define the environment variable PLX_SDK_DIR
     as follows:

	export PLX_SDK_DIR=/usr/local/GscApi/PlxSdk

     This should be added to the shell profile of the linux user(s) who will
     be building GscApi applications.

  8. Before running any sample applications, the PLX driver must be built and loaded.
     To build the desired PLX driver, cd to $PLX_SDK_DIR/Linux/Driver and run the
     builddriver script. Run builddriver with no command line options to see a usage
     statement that explains how to build the appropriate driver for your PLX board.
     After the driver is built, cd to $PLX_SDK_DIR/Bin and run the Plx_load script to
     load it into the kernel. Typing Plx_load with no command line parameters will
     display a usage statement that explains how to use the script to load your
     driver.

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.

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'.

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.

