## -*- mode: Text -*-
##
## Copyright (c) 2000, 2001 University of Utah and the Flux Group.
## All rights reserved.
## 
## Permission to use, copy, modify, and distribute this file
## for any purpose with or without restriction is hereby granted.
##

###############################################################################

The `msg' example demonstrates Knit bundletypes, renaming, and compound units.
The `msg' program is similar to the `hello' example.  In `msg', however, the
output message text is specified in a separate function, and the connections
between the functions in the program are woven by Knit.

The `configure' script in the topmost directory of the Knit source tree will
create the `GNUmakefile' for this example program.  After configuring and
building the Knit compiler itself, a simple `make' in this example directory
will run Knit to create the `msg' program.

The files that make up this example:

	GNUmakefile.in		The (template) Makefile for the program.
				For the most part, this file simply includes
				`GNUmakerules'.

	GNUmakerules		The ``real Makefile.''  The Knit compiler is
				run to create `knit_generated.mk', which
				contains the Knit-generated rules for building
				the `msg' program.  As part of creating this
				rule file, Knit processes the `msg.unit' file
				and outputs everything else that is needed to
				build the `msg' program.

	main.c			The main program.

	messages.c		A set of three functions, each returning a
				different Knit-relevant message string.

	msg.unit		The Knit unit file that describes the
				components of the `msg' program.  Read the
				comments in the file itself to see how the
				program components are defined and assembled.

###############################################################################

## End of file.

