_______________________________________________________________________________

	Java Virtual Shelf - WebWader
	Jean-Paul Le Fvre - JP.LeFevre@free.fr

	$Id: INSTALL,v 2.14 2001/06/23 08:27:57 lefevre Exp $
_______________________________________________________________________________

JVS Specific notes 
==================

Recompiling this package may not be very useful since it is written
in Java. There is no dependency on any system features.
It can be simply put to its destination directory (e.g. /opt/JVS).

However you can rebuild the java archive using the standard GNU procedure :
configure, make, make install.

The requirements are the following :
A java compiler and a java virtual machine 1.2 or better.

To enable XML support, the option --enable-xml must be passed to configure.
XML jar files must be available. See some explanations at :
http://jeanpaul.lefevre.free.fr/java/webwader/install.html#XML

The RBI (Remote Browser Invocation) package may enable different external
java HTML viewers if they are available. CLASSPATH must contain the
corresponding jar files. To verify your environment use :

	java org.demo.webwader.rbi.DisplayersProbe [-d] [displayer]

To recompile the JVS java files your CLASSPATH must also contain
the path to this src directory, e.g. :

         CLASSPATH=/home/lefevre/JVS/src:some_other_dir

Messages issued by javac are redirected to the file 'liste~' in each
source subdirectories. They are _NOT_ shown on screen.

If make(1) complains that some directories are missing, check the modification
time of Makefile, Makefile.in and Makefile.am. The file Makefile must be
the yougest, Makefile.am the oldest. If it is not the case touch the Makefile.
Sometimes it helps to launch make(1) again and again until all Makefiles are
correctly rebuilt. (Behaviour of automake is difficult to master ;)

The API documentation can be generated in the subdirectory 'doc/api'.
It is not built or installed automatically.

They are a few C programs (activate, open_url, print_url) which are
used to establish communication with the browsers. The sources are in
JVS/src/org/demo/webwader/etc. Once built they go to directory 'bin'.
Files .exe are executables for Win32. Other executables are for Linux x86.

To communicate with Amaya the official version from the W3 team
must be patched. See instructions on the WebWader web pages.

To communicate with SkipStone it is no longer necessary to patch
the original skipstone distribution.

Once the package is installed the variable JVS_HOME must be set
to the destination directory. The CLASSPATH must specify the
path to the installed jvs.jar.

The package WebWader is a subpart of the whole JVS. If files are
available (this is not the case for the public distribution of
WebWader) the compilation of the whole JVS can be enabled with 
the option --enable-full-jvs. The file configure-full.in must be
copied to  configure.in

If packages depending on Xml-RPC are needed the option --enable-xmlrpc
must be given to configure. A java implementation of the protocol is
provided at http://xmlrpc.helma.org.

If packages depending on MySQL are needed the option --enable-mysql
must be given to configure. The full JVS must be enabled.

If packages depending on Objectivity are needed the option --enable-objy
must be given to configure. The full JVS must be enabled.

If packages depending on Tomcat are needed the option --enable-tomcat
must be given to configure. The full JVS must be enabled.

If packages depending on Orbec are needed the option --enable-corba
must be given to configure. The full JVS must be enabled.


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, a file
`config.cache' that saves the results of its tests to speed up
reconfiguring, and a file `config.log' containing compiler output
(useful mainly for debugging `configure').

   If you need to do unusual things to compile the package, please try
to figure out how `configure' could check whether to do them, and mail
diffs or instructions to the address given in the `README' so they can
be considered for the next release.  If at some point `config.cache'
contains results you don't want to keep, you may remove or edit it.

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

The simplest way to compile this package is:

  1. `cd' to the directory containing the package's source code and type
     `./configure' to configure the package for your system.  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.

     Running `configure' takes awhile.  While running, it prints some
     messages telling which features it is checking for.

  2. Type `make' to compile the package.

  3. Optionally, type `make check' to run any self-tests that come with
     the package.

  4. Type `make install' to install the programs and any data files and
     documentation.

  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'.  There is
     also a `make maintainer-clean' target, but that is intended mainly
     for the package's developers.  If you use it, you may have to get
     all sorts of other programs in order to regenerate files that came
     with the distribution.

Compilers and Options
=====================

   Some systems require unusual options for compilation or linking that
the `configure' script does not know about.  You can give `configure'
initial values for variables by setting them in the environment.  Using
a Bourne-compatible shell, you can do that on the command line like
this:
     CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure

Or on systems that have the `env' program, you can do it like this:
     env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure

Compiling For Multiple Architectures
====================================

   You can compile the package for more than one kind of computer at the
same time, by placing the object files for each architecture in their
own directory.  To do this, you must use a version of `make' that
supports the `VPATH' variable, such as GNU `make'.  `cd' to the
directory where you want the object files and executables to go and run
the `configure' script.  `configure' automatically checks for the
source code in the directory that `configure' is in and in `..'.

   If you have to use a `make' that does not supports the `VPATH'
variable, you have to compile the package for one architecture at a time
in the source code directory.  After you have installed the package for
one architecture, use `make distclean' before reconfiguring for another
architecture.

Installation Names
==================

   By default, `make install' will install the package's files in
`/usr/local/bin', `/usr/local/man', etc.  You can specify an
installation prefix other than `/usr/local' by giving `configure' the
option `--prefix=PATH'.

   You can specify separate installation prefixes for
architecture-specific files and architecture-independent files.  If you
give `configure' the option `--exec-prefix=PATH', the package will use
PATH as the prefix for installing programs and libraries.
Documentation and other data files will still use the regular prefix.

   In addition, if you use an unusual directory layout you can give
options like `--bindir=PATH' to specify different values for particular
kinds of files.  Run `configure --help' for a list of the directories
you can set and what kinds of files go in them.

   If the package supports it, you can cause programs to be installed
with an extra prefix or suffix on their names by giving `configure' the
option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.

Optional Features
=================

   Some packages pay attention to `--enable-FEATURE' options to
`configure', where FEATURE indicates an optional part of the package.
They may also pay attention to `--with-PACKAGE' options, where PACKAGE
is something like `gnu-as' or `x' (for the X Window System).  The
`README' should mention any `--enable-' and `--with-' options that the
package recognizes.

   For packages that use the X Window System, `configure' can usually
find the X include and library files automatically, but if it doesn't,
you can use the `configure' options `--x-includes=DIR' and
`--x-libraries=DIR' to specify their locations.

Specifying the System Type
==========================

   There may be some features `configure' can not figure out
automatically, but needs to determine by the type of host the package
will run on.  Usually `configure' can figure that out, but if it prints
a message saying it can not guess the host type, give it the
`--host=TYPE' option.  TYPE can either be a short name for the system
type, such as `sun4', or a canonical name with three fields:
     CPU-COMPANY-SYSTEM

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 host type.

   If you are building compiler tools for cross-compiling, you can also
use the `--target=TYPE' option to select the type of system they will
produce code for and the `--build=TYPE' option to select the type of
system on which you are compiling the package.

Sharing Defaults
================

   If you want to set default values for `configure' scripts to share,
you can create a site shell script called `config.site' that gives
default values for variables like `CC', `cache_file', and `prefix'.
`configure' looks for `PREFIX/share/config.site' if it exists, then
`PREFIX/etc/config.site' if it exists.  Or, you can set the
`CONFIG_SITE' environment variable to the location of the site script.
A warning: not all `configure' scripts look for a site script.

Operation Controls
==================

   `configure' recognizes the following options to control how it
operates.

`--cache-file=FILE'
     Use and save the results of the tests in FILE instead of
     `./config.cache'.  Set FILE to `/dev/null' to disable caching, for
     debugging `configure'.

`--help'
     Print a summary of the options to `configure', and exit.

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

`--version'
     Print the version of Autoconf used to generate the `configure'
     script, and exit.

`configure' also accepts some other, not widely useful, options.

_______________________________________________________________________________
