This file contains instructions on how to build the latest version of uC++.
Presumably, you have just ftped the latest version.


>> REQUIREMENTS <<

uC++ requires at least:

1. version 2.7.2 of GNU C++ . (I've experienced problems with GNU C++ 2.7.0
   and 2.7.1).  KDB does NOT compile using other compilers.

2. version 4.0 of dmake, which is available by anonymous ftp from the following
   location (remember to set your ftp mode to binary):

	plg.uwaterloo.ca:pub/dmake/dmake40.tar.gz

   To build dmake, edit the variables in file ./unix/startup.h.  The environment
   variable MAKESTARTUP must specify the location of the startup.mk file, which
   contains all the implicit recipes.  This file is placed at the top level of the
   source directory after dmake is built.  If dmake is not being installed in a
   public location, set the value of MAKESTARTUP to
   {dmake-source-path}/startup.mk.

   After setting the MAKESTARTUP variable, type "make" to get a list of
   supported configurations or read the list in the top level make file.

   Type "make xxx", where xxx is one of the listed configurations, e.g., "make
   linux" to configure for Linux.

>> HOW TO BUILD uC++ <<

1. Before you build uC++, read the comments and edit the variables in the top
   level make file, ./Makefile.

2. Type "dmake" to get a list of supported configurations or read the list in
   the top level make file.

3. Type "dmake xxx", where xxx is one of the listed configurations, e.g.,
   "dmake sun-sparc-svr4" to configure for a SUN Sparc running Solaris. A CONFIG
   file is created and all Makefiles are modified with appropriate path names.

4. Type "dmake install" to compile and install uC++. To compile and install
   separately, type "dmake" to compile uC++ and then "dmake install" to move the
   necessary executables and libraries to the install location.

5. After installation is complete, there are a number of executables created in
   the directory defined by INSTALLBINDIR in the top level make file.  Add this
   directory to your command path to access the compilation command u++.  Do not
   move the executables from this directory, as the u++ command contains hard
   coded references to executables and runtime libraries that were set at
   installation time.

6. Type "dmake clean" to remove any temporary files created during
   installation.

>> NOTES <<

The file CONFIG is generated by the Makefile.  It contains definitions that are
specific to an installation on this type of machine.  This file is included by
many of the Makefiles in directories below this one.  Do not modify the CONFIG
file directly, rather, remove the CONFIG, modify the file ./Makefile, and start
at step 3 for building uC++.

>> AUTHORS <<

P. A. Buhr
R. A. Stroobosscher
