One or more source filenames may be specified, either by name or using the DOS wildcards * and ?. Filenames must be separated by a space.
Example
LF95 *.f90
If the files ONE.F90, TWO.F90, and THREE.FOR were in the current directory, ONE.F90 and TWO.F90 would be compiled and linked together, and the executable file, ONE.EXE, would be created because the driver found ONE.F90 before TWO.F90 in the current directory. THREE.FOR would not be compiled because its extension does not match the extension specified on the LF95 command line.
Source filenames are specified as a complete file name or can be given without an extension, in which case LF95 supplies the default extension .F90. In the absence of an option specifying otherwise:
Source files for a given invocation of the driver should not mix free form and fixed form. If files with both the .FOR or .F and .F90 or .F95 appear on the same command line, then all are assumed to use the source form the driver assumes for the last file specified.
The -fix and -nfix compiler options
can be used to control the assumed extension and override the interpretation specified
by the extension. See the
The default name for an object file is the same as the source file base name, with the .obj extension. By default, the object file is placed in the current directory.
Use the -o option to change the default object file name and
location. Note that the -o option is invalid when wildcards
are used to specify source files. See the
The default name for the executable file or library produced by the driver is based
on the first source or object name encountered on the command line. By default,
output files are placed in the same directory as the first file encountered. This
may be overridden by specifying the -OUT option with a new
path and name. The -OUT option is required when the first
file specified contains a wildcard. See the