next up previous contents
Next: Diary Up: Overview Previous: Style

System Environment

  The MFCF undergraduate Unix environment will be used as a common resource location. Team members who do any development off line (eg. on a home machine) must strive to keep their work shadowed on the MFCF machines as needed by the rest of the team. All work must ultimately compile and execute from a ``cold start'' in the GP environment on the MFCF machines. By this it is meant that the commands

alone, executed in the

directory with empty

directories, will compile all infrastructure code for the team's system, and the commands

alone, executed in the

directory, will compile, link-load, and produce an executable for the team's system. No extra shell scripts or elaborate make constructions should be needed or used.

Documents are to be formatted in a document preparation system of your choosing in cooperation with at least a spelling checker and ideally also a grammar checker. You must use at least a spelling checker.

Any diagrams being provided should be prepared on a diagram preparation system, ideally one included with the document system, or at least one whose products can be included digitally into the documents (rather than physically cut and pasted).

Code delivery will be accomplished by removing all executables, libraries, and links from the team's version of its src/Applications/* and src/Classes/* directories (make realclean is designed to accomplish this) and mailing a uuencoded, compressed, tar file of that directory and its subdirectories to the Instructor. (Do not use MIME inclusion; mail the uuencoded file as plain text.) Successful delivery will require that the Instructor can

and have a functioning system as a result.

next up previous contents
Next: Diary Up: Overview Previous: Style




Mon Sep 9 09:16:07 EDT 1996