#################################################################
# *** $RCSfile: README.src,v $
# *** $Revision: 1.5 $
# *** $Date: 1998/02/06 06:04:49 $
#################################################################

			Compiling MMIO
	Peter S. Shenkin, March, 1995, shenkin@columbia.edu

1.  See instructions at the top of Makefile.pro for making a new Makefile
    appropriate for your machine, and for making the code.  Make
    sure that the line in Makefile.pro containing the definition
    "MMIO_SRC_DIR = ." is not commented out (does not begin with a '#').

    To summarize the instructions, you'll have to first say:
        make makefile VERSION=something
    where "something" depends upon the machine you're compiling on;
    the list of possible "something"s appears in Makefile.pro.  This
    makes a version of the Makefile appropriate to your system.  Then
    you just say:
        make
    This will make the C and Fortran libraries, several test programs 
    and conversion programs, and the files README.C and README.Fortran
    that describe the C and Fortran APIs.

2.  The test programs cmmio and fmmio can be exercised by the scripts 
    ctest and ftest.  Each script performs four simple tests;  each should 
    end with a remark that the test was successful, followed by a brief 
    "diff" output.  The diff for each test might be null, or it could 
    consist of title lines that differ only in whitespace, or it could also
    exhibit coordinates that differ in the last significant figure (only).
    Any of these signifies a successful test.

    To use ctest and ftest, you need to have an environment variable
    defined called PAGER.  Example for csh:  "setenv PAGER more".

3.  Though there are flags in the Makefile for many platforms, only the
    flags for the following platforms are known to work;  the others 
    will nearly certainly require tweaking:
		SGI
		IBM
		OSF
		HP
		FUJITSU
		CRAY

    If you do successfully tweak flags and/or port to a new platform, 
    please convey your changes back to the author so that they may be 
    incorporated into the general distribution.

4.  Comments and suggestions for improvement will be cheerfully ignored.
    (Just joking :-) )

    
