.LP
The "Configuration" pane in \fBkraftsman\fP allows one to customize
any toolbox defined in the KHOROS_TOOLBOX file.  This customization includes 
setting the library and binary directory paths, setting library and include 
search paths, setting compiler defines, and defining C, Fortran, and X 
libraries for the toolbox.  Note defining C, Fortran, and X libraries should
include only those libraries that are contained within the toolbox.  Thus, you
should not define the C system libraries, F77 libraries, or the X libraries
in these fields.  These libraries are defined in the machine configuration
files for the main khoros system.  See Volume 2, Chapter 9 for more information
on the machine configuration files.
.LP
The different entries on the "Configuration" pane are as follows:
Note the fields with two lines imply that multiple entries are allowed.
For these fields, entries must be entered one per line.  A scroll
bar will appear if the number of entries exceeds two.  \fBAlso, the scrollbar
widget has a bug that causes it to ignore events from the mouse that change it.
In this case, use the arrow keys to move from entry to entry.\fP
.IP "Library Directory Path -"  20
Pathname to the directory that contains the libraries for the toolbox.  
This field \fBmust\fP be filled out correctly or your toolbox will not 
function.  The $(TB_NAME) is a variable substitute for your toolbox name.
Note that toolboxes created under Patch 4 were manually configured and thus
TB_NAME may have been changed.
.IP "Binary Directory Path -"  20
Pathname to the directory that contains the binaries for the toolbox.  
This field \fBmust\fP be filled out correctly or your toolbox will not 
function.  Again, the $(TB_NAME) is a variable substitute for your toolbox 
name, and, as noted above, it may have been changed for toolboxes created 
under Patch 4.
.IP "Library Search Paths -"  20
The pathnames to the directories that will be searched while compiling 
routines within the toolbox.  This field also \fBmust\fP be filled out 
correctly for your toolbox to work correctly.  $(LIBDIR) refers to the
library directory path field filled out above.   
.IP "Include Search Paths -"  20
The pathnames to the directories that will be included while compiling 
routines within the toolbox.  As above, this field must be filled out
correctly for the toolbox to work.
.IP "Compiler Defines -"  20
The defines passed to the compiler when compling routines within the
toolbox.  This field is optional.  Note \fBDO NOT\fP put the -D in 
front of the define name; this will be added by \fBkraftsman\fP when 
writing the configuration file.  For example, if your source code
requires the define 'LOCAL', then the word 'LOCAL' should be put on a line
in this field.  \fBKraftsman\fP will insert a '-D' on the front of each entry
in this field when it writes out the configuration file.
.IP "Toolbox Libraries -"  20
C libraries that are managed by the toolbox.  This field must have
a library name for each 'C' library in the toolbox.  If the toolbox does
not have any libraries, leave it blank.  Note \fBDO NOT\fP include the '-l'
flag with the library name (e.g. enter 'mylib' not '-lmylib').
.IP "Fortran Libraries -"  20
Names of Fortran libraries that are managed by the toolbox.  This field must
have an entry for every fortran library in the toolbox.  Again, if it does
not have any Fortran libraries, just leave this field blank.  Again, only
enter the library name, \fBDO NOT\fP include '-l'.
.IP "X Libraries -"  20
This field contains the names for the X libraries that are managed by 
the toolbox.  Any library which makes a call to an X routine would be included
in this category.   As before, if there are not any X libraries, leave
this field blank. \fBDO NOT\fP include '-l'.
.LP
Once the desired fields are set, the configuration file can be updated
by pressing the "CONFIGURE TOOLBOX" button.  Note when adding entries to
the "Toolbox Libraries", "Fortran Libraries", and "X Libraries" fields,
the first line on the pane will be the first library to be loaded.  Also,
all libraries defined in these three fields will be loaded before the
khoros and system libraries.
.sp
.LP
One more thing to note: Configuration does not deal with multiple 
architectures.  You must change the machfiles by hand as detailed in
Volume 2, Chapter 9, \fIConfiguration Management\fP.  More information 
on toolboxes and their configuration can be found in Volume 2, 
Chapter 1, \fIWriting Programs\fP.
