
PLEASE NOTE: all the configuration files are now located in ./templates


-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
	Setting Up A Compile And Actually Compiling
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

The only file you should really change/edit before compiling are
the local and hostname specific configuration files in the the
./templates directory.  All of the files refered to below
actually live in this ./templates subdirectory, except for
the site.def file -- which is build automatically in the
toplevel directory..

  templates/local.config
	** this file used to be called template.site, but
	** that caused me some confusion -- JM 6-Oct-94

Examine the templates/template.<arch> appropriate to your setup
and then change anything you want changed by copying the lines
you want to change to templates/local.config or
templates/<hostname>.confgi and editing them to say what you
want.  You can even just "cp template.<arch> local.config" and
then edit what you want.

**** Please DON'T change the template.<arch> files.. ****

Once this is done (in theory), you can compile by typing:

  ./Build all

and have the whole thing will be built for you.

Installation is not quite automatic. Essentially either add
./xdowl, ./apps, ./Tools  and ./tcllib to your path or else
use the Install script in this directory to move all the
executables to a public place (edit Install to tell it where).

Once again, in case that wasn't completely clear:

   templates/template.SunOs = standard configuration for SunOs 4.1.x
   templates/template.Linux = same for Linux
     templates/local.config = your personal customizations (please save a
			      copy of this file before upgrading versions).
  templates/HOSTNAME.config = host (by name) specific config.. optional.
			      (you can use this instead of local.config
			      to avoid geting your config changed with
			      new releases).
                 ./site.def = current configuration data (./Build script
			      makes me and EVERYTHING uses me)

template.<machine> + local.config + <hostname>.config = site.def

N.B. site.def is automatically generated by the Build script each
     time you run Build -- DO NOT MAKE CHANGES TO site.def. They will
     be lost the next time you run Build.




-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
	What's What?  What's Where??
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

The directories:
	templates/
	  All the configuration information available for building..
	Docs/
	  Whatever minimal documentation there is..
	libsrc/
	  Dowl library source code (everything to build libdowl.a)
	xdowl/
	  Sources for xdowl, xdbrowser, xdplot etc. These applications are
	  special since then must know about the set of modules and plotters
	  you would like to include in the tool dock.
	apps/
	  Application sources (everything except xdowl, xdbrowser and xdplot)
	drpmproc/
	  DSP support for sparc
	s56proc/
	  DSP support for sparc-10 using BCE's "new and improved" drivers
	ad/
	  X-Resource tables (for generating XDowl and XDowl-color)
	Tools/
	  Useful c-shell, bourne-shell and tk/tcl scripts. Most of these
	  are for looking at datafiles in odd ways, printing etc. There's
	  nothing magic here -- just things I tend to use frequently and I
	  think others might find useful.
	some-cal/
	  Some sample calibration tables

