LINK386 is used to combine object files and standard library files into a single executable file. LINK386 also generates DLLs and device drivers.

LINK386 uses the following files as input:

• One or more object files that are linked with any optional library files to create the executable file. Object files usually have a .OBJ extension.

• One or more library files. The library files contain object modules that are linked with the object files to create the executable file. Library files usually have a .LIB extension.

• A module definition file. The module definition file provides information to LINK386 about the executable file or dynamic link library file it is creating. The module definition file usually has a .DEF extension.

LINK386 produces three types of output files:

• An executable file. This executable file runs under OS/2 whenever you specify a module definition file that has a NAME statement. The executable file usually has an .EXE extension.

• A dynamic link library file. A dynamic link library is produced whenever you specify a module definition file that has a LIBRARY statement. A dynamic link library file usually has a .DLL extension.

• A device driver file. A virtual or physical device driver is produced whenever you specify a module definition file that has the VIRTUAL DEVICE or PHYSICAL DEVICE statements. A device driver file usually has a .SYS extension.

Note:

Three additional options are available with the OS/2 Warp Toolkit: