### Link from the Command Line

To start the linker, type `ilink` followed by any sequence of options, file names, or directories, separated by space or tab characters. You can also use wildcard characters to specify multiple object files.

    ILINK  [option] [filename] [directory]  [/LOGO | /NOLOGO] @ responsefile

The linker recognizes the input as follows:

Options | Start with a / or - character.
Directories | End with a / or \ character.
Response files | Start with the @ character.
Export files | End with the .exp extension.
Library files | End with one of these extensions: .a .imp .lib
Resource files | End with the .res extension.
Object files | Any other input. You must enter at least one object file.

When you invoke the linker from the command line, the linker assumes that any input it cannot recognize as other files, options, or directories must be an object file. The linker does not assume the .obj extension for a file: if you specify a file with no extension, then the linker looks for that file with no extension.

If the linker cannot find a file, it stops with an error.

#### Examples

    ILINK /MAP:funlist fun.obj text.obj table.obj care.obj xlib.lib

> This command links the object files fun.obj, text.obj, table.obj, and care.obj. If any references are not resolved by the objects, the linker will look for a definition in xlib.lib and in the default libraries. Since there is no name provided for the executable file, it is named fun.exe, taking the filename of the first object file and the default extension .exe. The linker also produces a map file, funlist.map.

    ILINK /MAP main.obj getdata.obj printit.obj

> This command links the files main.obj, getdata.obj, and printit.obj into an executable file named main.exe, and produces a map file named main.map.

Set Linker Options

Summary of Linker Options
Linker Search Rules
Linker Error Messages