A 'make' at the top level directory of the SWORD package should build the
libraries necessary for building any of the frontends.  The libraries will
be built in the ./lib directory.  If you encounter an error, you may need
to change a setting in the Makefile.cfg file.  Most obviously watch for:
CC=gcc or CC=egcs

After the libraries are built, one, then, may proceed to the ./apps
directory.  The most basic application that is stable and easy to
build is the cheatah frontend (./apps/X11/cheatah).  These frontends
each have their own make system, so read the help in their respective
directories if a problem is encountered while building.

___________________________________________________________________________

To be useful the software needs to find SWORD 'modules' installed somewhere
accessible.  These module plugins consist of Bible texts, commentaries,
dictionaries, and the like.  New plugins are constantly being added.  They
may be obtaining from:
http://www.crosswire.org or various mirrors
A file named 'mods.conf' contains all configuration information regarding
the installed modules available to the API.  The format of mods.conf is
fairly straight-forward, and most modules come with their own .conf file,
of which the contents may be appended to the mods.conf file.

The API looks for its module configuration in the following sequence:
	./mods.conf
	$SWORD_PATH/mods.conf
	$HOME/.sword/mods.conf
	or finally from information found in a system-wide configuration file
		/etc/sword.conf in the format:
			[Install]
			DataPath=/where/your/datafiles/are/installed
		then the API will look for DataPath/mods.conf

Sample mods.conf files can be found in: .../sword/samples

