Prerequisite Tools
==================

If you're working from CVS you'll need the following tools:

	- autoconf-2.59
	- automake-1.8.2
	- libtool-1.4.3
	- pkgconfig-0.15.0

They all need to be installed in the same prefix, whether it is the
standard /usr or /usr/local, or in some other directory like
~/install/autotools-gcjwebplugin.

Use exactly these versions; we'll keep this list up-to-date as the
prerequisites change.

Building gcjwebplugin
=====================

The plug-in links to libgcj and Glib and requires headers from
Mozilla's source tree.  You will need to set PKG_CONFIG_PATH if either
libgcj or pkgconfig is installed in a non-standard location.
PKG_CONFIG_PATH is a colon-delimited list of directories where
pkg-config may find .pc files.

For example:

export PKG_CONFIG_PATH=$(libgcj_prefix)/lib/pkgconfig:/usr/lib/pkgconfig:$PKG_CONFIG_PATH

Most distributions install Glib by default, so it shouldn't require
any special handling.

configure runs mozilla-config to locate header files that the plug-in
requires, so you'll need:

export PATH=$(mozilla_build_dir)/dist/bin:$PATH

To build the plug-in and install it in ~/.mozilla/plugins:

./configure && make && make install

Building in a directory separate from the source tree is supported.

See the output from

./configure --help

for more configuration options.

If you build from CVS you will need at least autoconf 2.59, automake
1.7 and libtool 1.5 to generate the configure scripts.

Loading gcjwebplugin in Mozilla
===============================

After installing gcjwebplugin, add $(libgcj_prefix)/lib and
$(mozilla_build_dir)/dist/bin to LD_LIBRARY_PATH.  Also make sure that
appletviewer is in your PATH.  gcjwebplugin should now appear on
Mozilla's "Help->About Plug-ins" page.
