NAME.rst source code needing saw,sat, ratfor and fortran passes NAME.rs source code needing saw, ratfor and fortran passes NAME.rt source code needing sat, ratfor and fortran passes NAME.r source code needing ratfor and fortran passes NAME.f fortran NAME.rscm source code needing saw, ratfor and CM Fortran 90 passes NAME.rtcm source code needing sat, ratfor and CM Fortran 90 qpasses NAME.rcm source code needing ratfor and CM Fortran 90 passes NAME.fcm source code in CM Fortran 90 NAME.o object file, ready to be linked NAME.x executable (sometimes without .x) NAME.ps postscript NAME.ps.save precious postscript, not to be burned. NAME.v vplot (intermediate plot language) NAME.v.save precious vplot, not to be burned. NAME.v3 vplot movie NAME.v3.save vplot movie, precious NAME.H data history file. NAME.p process parameter file NAME.orig "restore" evokes "cp NAME.orig NAME" NAME.A history file pointing to movie bytes. NAME.warning a file for miscellaneous explanations used in dialogs.
SEP.obj.rules and SEP.prog.rules are smart enough that simple linking jobs are done for you with no assistance. Thanks to Dave Nichols, these rules know about the different compiler flags and library names on different machines. Often several files must be compiled separately and linked together. Below is how we create the executable myprog.x which links a fortran main with some .o files.
#define MYPROG mymainprog.o sub.o fun.o myprog.x : MYPROG FLINK(MYPROG, myprog.x)