
See the documentation in doc/setup.txt for details on how to use the
contents of this directory to configure the dotools for use with your
own 


When the dtools package is installed, most of the setup directory is
copied to $prefix/share/dtools-wave-setup, and Makefile_user from the
distribution package is copied as $prefix/share/dtools-wave-setup/Makefile.
The intention is that the installer or other users of this package
will copy the dtools-wave-setup directory and edit the Makefile to
build waveforms for their particular environment.

As installed, dtools-wave-setup/Makefile is set up to build waveforms
in a directory dtools-waves/hpcmos14-new.  The idea is that we can
compare these with the prebuilt waveforms in dtools-waves/hpcmos14.

Another way to code all of this would have been to have "make install"
in setup build waveforms for a user's technology when the package is built.
I chose not to do this for several reasons:

- The installer might want to just experiment with the distributed prebuilt
waveforms and technologies before setting up their own.

- I don't want to complicate the "configure" process with a lot of
knowledge about what cmos models are installed.

- The makefile and circuit files might need editing to adapt to a
particular situation.  We're assuming that the installation will be
done by by an expert CMOS designer and spice user, but not necessarily
an expert with autoconfigured packages in general or the dtools
package in particular.

- The installer may want to go back and configure several technologies,
perhaps long after doing the actual dtools configuration.

