LINK Command Files
The latest version of this topic can be found at LINK Command Files.
You can pass command-line arguments to LINK in the form of a command file. To specify a command file to the linker, use the following syntax:
LINK @commandfile
The commandfile is the name of a text file. No space or tab is allowed between the at sign (@) and the filename. There is no default extension; you must specify the full filename, including any extension. Wildcards cannot be used. You can specify an absolute or relative path with the filename. LINK does not use an environment variable to search for the file.
In the command file, arguments can be separated by spaces or tabs (as on the command line) and by newline characters.
You can specify all or part of the command line in a command file. You can use more than one command file in a LINK command. LINK accepts the command-file input as if it were specified in that location on the command line. Command files cannot be nested. LINK echoes the contents of command files, unless the /NOLOGO option is specified.
Example
The following command to build a DLL passes the names of object files and libraries in separate command files and uses a third command file for specification of the /EXPORTS option:
link /dll @objlist.txt @liblist.txt @exports.txt