When the compiler is invoked with the /LINK option, for example
FTN95 MYPROG /LINK
the linker is automatically invoked after compilation is com plete (assuming, of course, that no compilation errors have occurred). The resultant object code is loaded and a corresponding .EXE file is produced (a .OBJ file is not saved). The example above would create a run file called MYPROG.EXE .
If you wish to load other relocatable binary files, in addition to that produced by compilation of the named source file, the /LIBRARY compiler option (or the corresponding directive) should be used.
Relocatable binary libraries and input files
The use of the /LGO and /LINK options is not restricted to programs that require only the FTN95 library. Other system or user relocatable binary (RLB) libraries and RLB input files can be specified by using one or both of the following methods:
By using the /LIBRARY option in the FTN95 command line. For example:
FTN95 MYPROG /LGO /LIBRARY GKSLIB
By using a LIBRARY directive (which, in fixed format, must commence at or beyond column 7) in the source file.
where <pathname> is the name of the file. For example:
Use of a LIBRARY directive ensures that no RLB library or input file is forgotten when loading a program as the directives are always pre sent in the source file.
If a library filename does not include path information, the current directory is searched, followed by the directory containing the FTN95 compiler.
The compiler will automatically search first for an RLB library or RLB input file with a name suffixed by .OBJ, and then for the un suffixed filename, even if the library or input filename specified in the FTN95 command does not contain the suffix.
Dynamic link libraries are not specified on the LIBRARY directive. Under Win32, DLLs are normally located either in the directory for the executable or on the PATH.