.LP
This section explains what the user must manually do to completely configure
a new toolbox after 
\fBkraftsman\fP has been used to create a toolbox framework.  The "CREATE"
operation sets up a minimal configuration.  You must follow
the instructions below before \fBkinstall\fP will work properly.
.PP
In this discussion, "{toolbox_name}" means the name of your new toolbox,
and {toolbox_home} means the path to your toolbox.
.PP
A source configuration file has been set up that will work for a
basic toolbox.  This file will work "as is" if you do not need to
support multiple architectures.  If this is not true, you should go
inspect this file,
.br
\f(CW{toolbox_home}/repos/config/src_conf/{toolbox_name}_mf\fP 
.br
and see Chapter 9 for special instructions.
.LP
At this point, it is assumed that you have successfully created the basic 
toolbox source tree and configuration files.  Please continue:
.IP "1."
\fBkinstall\fP needs a directory(s) in which it can install a program.
In  {toolbox_home}/src, you will need to create
any directories that you might need - we suggest a Lib directory if
you will be creating a new library for your new programs to call, and one
directory for each program, named for that program.  In the case that you 
plan to add programs in different application domains, we recommend that
you create a directory for each application domain, and then have the 
associated program directories located in the application domain directories.
.IP
It is assumed that you will use \fBkinstall\fP to install the new routine
into your toolbox.  You will need to follow this example to set up the
toolbox source tree before \fBkinstall\f can be used.
.sp
Suppose the "vfrog" program is the first program to be installed
into the new toolbox. And, you want "lvfrog.c" code to become part of a library.
The first thing to do is copy the "lvfrog.c" code into the library directory
in the source tree. Next you must create an Imakefile and Makefile. The
following commands will create the Imakefile and Makefile for you:
.sp
.RS
.nf
\f(CW% imkmf -name {library_name} -type lib -toolbox {toolbox_name}\fP
.br
\f(CW% makemake
.fi
.RE
.IP
Where {library_name} is the name of the library and {toolbox_name} is the name
of your toolbox. This must be done so that \fBkinstall\f does not fail during
the installation of the first routine.
.IP
You must now tell the toolbox about your library.  In order to do this,
run \fBkraftsman\fP, and select the "Configuration" pane, and enter
{toolbox_name} in the space provided.  At this point, add your library
name to the Toolbox Libraries field.
.IP "2."
Now, your toolbox is ready for use.  Remember that any time you use any
of the Khoros tools, such as \fBimkmf, kinstall, ghostwriter\fP etc, you 
\fIMUST\fP provide the name of your new toolbox.  To be on the safe side,
any time you use a Khoros utility, consult the usage statement by using the
[-U] argument.  If \fIany\fP utility lists [-toolbox] as an option - USE IT!
.IP "3."
Once you have created your toolbox source tree,  you must create Imakefiles
and Makefiles for the toolbox source tree.  This is done by
using \fBimkmf\fP.  In \f(CW{toolbox_home}/src\fP, and in any application
domain directories that you may have, execute:
.sp
\f(CW% imkmf -type dir -toolbox {toolbox_name}\fP
.sp
\f(CW% makemake\fP
.sp
Note, makemake may give you the following errors:
.br
\f(CWsh: syntax error at line 3: `;' unexpected\fP
.br
\f(CWmake: Fatal error: Command failed for target `depend'\fP
.sp
You can ignore this error for now. It is caused because makemake wants to
descend into all subdirectories, but no Imakefiles and Makefiles
have yet been created in the subdirectories.  As you add programs and
directories, this error will no longer appear.
.IP "4."
Develop your new programs in your work directory described in the former 
sections of this chapter.  Don't forget to use the [-toolbox] option 
to \fBghostwriter\fP.
.IP "5."
If you are writing a vroutine, use \fBkinstall\fP to install your new program 
in your toolbox.  Don't forget to  use the [-toolbox] option.  If you are
writing an xvroutine, you must install your new program by hand.  Instructions
for this were given earlier in this chapter. 
.IP "6."
Add the \f(CW{toolbox_home}/bin\fP directory to your path (either in your 
".cshrc" file or in your ".login" file) so that you can access your new routine.
.sp 2
.SH
DON'T FORGET ...
.IP 1.
After setting up a toolbox and defining the bin directory location, add
this path to the toolbox bin directory to your path. Modify your ".cshrc"
or ".login" file and add the toolbox bin directory to your path.
.IP 2.
If any other libraries are created in the toolbox and programs need
to load against them, those libraries must be added to the 
imake definition file via kraftsman's configuration pane.
.IP 3.
Any time the you modify the configuration of the imake definition file
for the toolbox, you should do:
.br
\f(CW% make Makefile Makefiles\fP
.br
in the top level source directory of your toolbox to update all the 
Makefiles to take advantage of the changes.
.IP 4.
When using the any of the Khoros tools to manage a toolbox, the [-toolbox] 
option MUST be specified.
