How to configure and compile GWXLIBS
====================================

Hopefully, compiling GWXLIBS should be a simple matter of running the
``build'' script, either interactively, or with command line arguments
to drive the configuration and installation process.  This script
only supports a limited number of systems though, so for a new system
you should either create a new build script in the bldtools/ directory,
or examine what the build script does and perform the steps manually
in each directory in the source/ directory.

To see which operating systems are supported by the build script, execute
     build list

For help on the various command line argument (also described below), execute
     build help

To execute the build script interactively, simply execute
     build

For automated builds, you can answer all of the build questions on the
command line.  The options are passed to the build script in the same
order that they are asked for when run interactively.  The order is:

  system
    This is the name of the supported operating system build.  Run the
    command 'build list' for a list of all supported systems. Note that
    compiler variations will be listed as different systems.
  prefix
    This is the installation prefix. Typically, this would be either
    /usr or /usr/local. Note that the system specific files will use
    this value to specify other directories. Although autoconf allows
    you to fine-tune the location of various paths, this top level
    build script does not. You can only specify the base prefix, except
    as noted below.  If you leave this blank, the default prefix defined
    in the host configuration file will be used.
  root
    Specify the installation root. Unless you are installing onto a live
    system, this is the path under which all files will be stored. This
    is passed to the various make scripts as DESTDIR. If you will be
    installing onto a live system, specify this as an empty argument ("").
  build
    The directory in which the build will take place. If you will be using
    the same source tree for multiple architecture builds, you should not
    build inside the source tree. If, however, this is a single build, you
    can build in place by specifying this as an empty argument (""). If you
    specify an alternate build directory it must be an absolute path.
  configure
    Any additional arguments you want to pass to configure. If you have
    more than one option the entire set of options must be quoted as a
    single argument. If you do not have any, leave this as an empty
    argument ("").

There are a few special commands you can give to the build script. These
typically invoke the lower level make scripts with the specified argument.
The currently supported commands are:
  build clean
    Clean up after a build. This does not remove files created during the
    configuration process, it simply removes all of the build files.
  build clobber
    Same as build clean but also removes all of the files generated by
    the configuration process.
  build package
    Invokes a platform-specific packaging script to create installable
    images for the platform specified. This can only be run after a
    full successful build.
