LINK Help (linker.hlp) (
Table of Contents;
Topic list)
LINK Response File
◄Up► ◄Contents► ◄Index► ◄Back►
─────LINK───────────────────────────────────────────────────────────────────
You can supply input to LINK in a response file. A response file
is a text file containing the input LINK expects on the command
line or in response to prompts. Use a response file to hold
frequently used options or responses or to overcome the
128-character limit on the length of a DOS command line.
See: ◄LINK Command Line►
◄LINK Prompts►
◄<objfiles> Field►
◄<exefile> Field►
◄<mapfile> Field►
◄<libraries> Field►
◄<deffile> Field►
Usage
Specify the name of the response file in place of the expected
command-line input or in response to a prompt. Only one response
file can be used. Precede the name with an at sign (@), as in:
@responsefile
LINK does not assume a default extension.
Contents of the Response File
Each input field must appear on a separate line or be separated
from other fields on the same line by a comma. Extend input to a
new line by using a plus sign (+) at the end of the current line.
You can represent a blank field by either a blank line or a comma.
Use a semicolon (;) to choose default responses for all remaining
fields, as with command-line input and responses to prompts. LINK
ignores any text in the file after the five expected fields are
satisfied or a semicolon is specified. If the response file does
not give input for all remaining fields and does not end with a
semicolon, LINK prompts for the rest.
Options can appear anywhere in the response file before the last
input or semicolon.
See: ◄LINK Options List►
◄Using LINK Options►
LINK displays responses after prompts on the screen. If an entry
in the response file is not acceptable to LINK, it prompts for a
valid response. The /BATCH option disables some prompts.
See: ◄/BATCH Option►
-♦-