Huit Files

Huit emulator
=============
Compiling huit
--------------
First, download environ_srce-1.10.tgz, which contains support and 
diagnostic functions used by huit, together with test harnesses,
scripts and test data. It creates an 'environ' directory and unpacks 
into it. 

Edit the Makefiles as needed to suit your environment. As issued they
will compile everything in situ and 'make install', which should be
run with sudo, will install libenviron.a in /usr/local/lib and the header
files in /usr/local/include. Then run 'make all' to compile the library
and 'sudo make install' to install it.

Documentation, in environ_docs-1.10.tgz, consists of a set of HTML pages. 
It unpacks into 'environ/docs'. Opening environ/docs/index.html with a 
web browser displays the complete documentation set. You can leave it there
or move the complete set of HTML pages to a more convenient location.

Once the environment library is installed, create the 'huit' directory,
and pull the git repository containing huit into it. All compilations are 
run from the huit/srce directory. This leaves the dynamic libraries and 
executables in huit/srce/bin. 

All testing etc is run from the huit/srce directory. Running 'allregress'
checks that all emulator modules are working correctly: you should see 
only a list of scripts and the time taken to to run them if the tests are
all passed. 

Running huit in the development environment 
===========================================
The 'bin/huit -?' command shows the command line options and arguments 
while 'bin/huit' should cause the emulator to run the Flexbug monitor 
module. This displays an ID line and prompts for input: the '?'
command shows the available commands. The Flex OS module is started by
enytering the Flexbug '+' command and acts similarly: the Flex 'builtins' 
command shows help details for the available builtin commands.