Basic Installation
==================

    For more information specific to this package, please read the README
file. This source code distribution  is autoconfiguring and you should be 
able to compile it and install it without manual interventions such as 
editing Makefiles, configuration files, and so on. These are generic 
instructions for people who are not familiar with installing autoconfiguring
software.

The simplest way to compile this package is to enter the source code
main directory and do the following:
   
  1. Configure the source code by typing:
        % sh ./configure

     If you're planning to install the package into your home directory
     or to a location other than `/usr/local' then add the flag
     `--prefix=PATH' to `configure'. For example, if your home directory  
     is `/home/luser' you can configure the package to install itself there
     by invoking:
        % sh ./configure --prefix=/home/luser
     
     While running, `configure' prints some messages telling which
     features is it checking for. 

  2. Compile the package by typing:
        % make
     Running `make' takes a while. If this is a very large package, now
     is the time to go make some coffee.
     
  3. Some packages are bundled with self-tests for source-code 
     verification. If this package includes such tests, you can 
     optionally run them after compilation by typing 
        % make check

  4. Type `make install' to install the programs and any data files and
     documentation. Type `make uninstall' to undo the installation.
     During installation, the following files go to the following directories:
        Executables          -> /prefix/bin
        docs and samples     -> /prefix/share/doc/java2html
        conf files           -> /prefix/share/java2html
     where `prefix' is either `/usr/local' or the PATH that you specified
     in the `--prefix' flag.

     If any of these directories do not presently exist, they will be
     created on demand. 

     If you are installing in your home directory make sure that 
     `/home/luser/bin' is in your path. If you're using the bash shell
     add this line at the end of your .cshrc file:
        PATH="/home/luser/bin:${PATH}"
        export PATH
     If you are using csh or tcsh, then use this line instead:
        setenv PATH /home/luser/bin:${PATH}
     By prepending your home directory to the rest of the PATH you can
     override systemwide installed software with your own custom installation.

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

Problems
========
   You shouldn't get any problem, because configure should succeed in
finding everything you need, but some Unix systems may not have some
right settings, especially for C++ directories: one problem encountered
was on a Sparc: C++ couldn't find include files (such as iostream.h).
You'll just have to search for one of them (e.g iostream.h) 
and then assign that directory to INCLUDE env.var specifying -I option,
e.g. if include files are in the directory /usr/include/g++-include, type

  export INCLUDE=-I/usr/include/g++-include

under bash shell or

  setenv INCLUDE -I/usr/include/g++-include

and run configure once again.
  For instance on that Sparc the directory was 
/export/opt/FSFlibg++/lib/g++-include !!! 

  If this doesn't work, please mail me your problem at bug-java2html@gnu.org.

Compiler configuration
======================

   The `configure' shell script is responsible for choosing and configuring
the compiler(s). 

The following options allow you to specify whether you
want to enable or disable various debugging mechanisms:

`--enable-warnings'
      Make the compilers very picky about warnings. Try this whenever you
      write new code since it may catch a few bugs. This is not active by
      default because all too often warnings can be too picky and scare
      the end-user.