This should allow you to get your Analysis Control code linked into an executable.
We assume you're using
Execute the following commands:
This procedure differs somewhat from that documented in CDF
build_job runs as in the note. However,
to give the command "
WRITE [filename].F" when you are ready
to write the file, instead of giving it a .cdf extension. (In
particular do not use
EXIT to save your file; use
QUIT and save yourself some confusion.)
The next step is to turn the ".F" file produced by
build_job into a real FORTRAN file; this
is done with the command
If your files have .f or .for extensions, you must rename them
with the upper case extension .F.
gcc needs this so it knows
to run the preprocessor on them.
The command is:
g77 -I$CODE/cdfsoft1/development/include -DUNIX
-fno-second-underscore -fdollar-ok -c yourfile.F [-O2] [-g]
where the optional argument
-O2 will optimize the output and
-g will add debugging information.
Repeat as necessary until all the .F files are compiled. This method produces files sharing the name of the code files but with .o extensions.
OBJECTS = myfile1.o myfile2.o ...
myfile?.oare the names of the .o files produced in step 2, and the first line reads
EXENAME = target
targetis the name of the executable you want.
make. It should produce your executable.
Experimentally, you can use the Makefile to run expand for you. Get this version of expand that does not overwrite the .CDF file, edit the line EXPAND in the Makefile to point to it, save the output of build_job to .CDF files, and make.