IOAPI 2.2 - 30 Sep 2004

 The I/O API Version 2.2 source code, documentation, and binary object 
 libraries for certain platforms are available at:

     http://www.baronams.com/products/ioapi/AVAIL.html

 This web site shows how to build IOAPI libraries in detail.  The following
 is a summary:

   1) Untar the downloaded file:

         tar xvfz ioapi_22.tar.gz

   2) Determine your machine architecture and the available Fortran and C
      compilers:

         The command "uname -a" provides machine architecture information.

   3) Determine the supported architecture and compilers:

         ls -al Makeinclude.*

         The Makeinclude file extensions are named according to the type of
         architecture and compiler.

         For instance, if your machine is a Linux box with Pentium processor 
         and you are using an Portland Group Fortran compiler (pgf90), you should
         use Makeinclude.Linux2_x86pg. 

   4) Set up the library directory:

         setenv BIN <lib>

         where <lib> is the file extension you determined in step #3

         Using the previous example, you would type "setenv BIN Linux2_x86pg"

   5) Select the no-couple Makefile:

         cp Makefile.nocpl Makefile

   6) Build the library by typing:

         make

   Note: 1. If the compilers you chose are not found, check Makeinclude.<lib>
            to see whether the compiler paths are set correctly.
            
         2. In our compilation, we used pgf90 and gcc.  We made the following changes
            to the Makeinclude.Linux2_x86pg file ("patch" style difference):

            18c18,19
            < CC = pgcc
            ---
            > #CC = pgcc
            > CC = /usr/bin/gcc
            22c23,24
            < OMPFLAGS  = -mp
            ---
            > #OMPFLAGS  = -mp
            > OMPFLAGS  =
            24,25c26,27
            < COPTFLAGS = -O2 -fast
            < FOPTFLAGS = -O2 -fast
            ---
            > COPTFLAGS = -O2 -ffast-math -DIOAPI_NO_STDOUT
            > FOPTFLAGS = -O2 -fast -DIOAPI_NO_STDOUT
            27,29c29,31
            < FSFLAGS   = -Msave
            < # ARCHFLAGS = -DFLDMN=1 -DAUTO_ARRAYS=1 -DF90=1
            < ARCHFLAGS = -DFLDMN=1 -DAUTO_ARRAYS=1 -DF90=1 -Msecond_underscore # -Mnoupcase
            ---
            > FSFLAGS   = -static
            > ARCHFLAGS = -DFLDMN=1 -DAUTO_ARRAYS=1 -DF90=1
            > #ARCHFLAGS = -DFLDMN=1 -DAUTO_ARRAYS=1 -DF90=1 -Msecond_underscore # -Mnoupcase

            Note: You can change the file by using the Unix "patch" utility.
            Cut the indented section listed above and paste into a file, say "mod."
            Then type "patch <script> mod."

            The -DIOAPI_NO_STDOUT in COPTFLAGS and FOPTFLAGS in the
            Makeinclude.<lib> file avoids verbose run-time output messages.

         3. The library is created in the subdirectory <lib> (see step #4).

   7) The IOAPI needs to be installed in a location that is accessible to the CMAQ scripts. 
      The environment variable M3LIB points to the directory $M3HOME/lib within the CMAQ directory 
      structure where all libraries needed by CMAQ should be located by default.  If you do not 
      install the IOAPI directly into $M3LIB, you will have to either copy the $BIN directory 
      containing the compiled library and object files to $M3LIB/ioapi_22 or create a symbolic link to 
      the ioapi_22 directory from $M3LIB. Note that in addition to the compiled library and object 
      files, CMAQ also requires a group of IOAPI include files located in the ioapi_22/fixed_src 
      directory; this directory needs to be included in your $M3LIB/ioapi_22 directory as well. 
      The $M3LIB/ioapi_22 directory must contain a directory named $BIN (see above) with the 
      compiled library and object files and another named fixed_src/ containing the IOAPI include 
      files from the directory with the same name included in the IOAPI distribution.