For maximum flexibility and ease of use, the assembly language linker, WL32, supports response or linker script morphing commands. Morphing capability allows WL32 to read the link or response files and scripts of any linker without changing those files to conform to WL32's commands and options. This capability includes support for both positional (e.g. Microsoft Link and TLink) and freeformat (e.g. RTLink) link files and scripts.


To use the morphing feature, place the morphing commands in a linker configuration definitions file and specify the file to WL32 through the /lc:<filename> option. If a morphing command configuration definitions file is not found in the current directory, WL32 will look for the file in the directory containing WL32.EXE (i.e. the invocation path of WL32).

With all morphing commands in a configuration file, case is significant and WL32 returns an error for a lowercase command. However, case is not significant for the <string> or <option> listing that is translated or morphed into an instruction understood by WL32. For example, LIB=LIBNAME and lib=LIBNAME are valid definition file lines, LIB=libname and lib=libname are not. Only one command may be made per linker definition file line.

An asterisk (*) character placed at the end of the <string> instructs WL32 to ignore the entire response file or command line after processing <string>. This is commonly used to ignore characters after a superfluous command, such as MODULE.

A plus (+) character placed at the end of the <string> instructs WL32 to ignore the rest of the current option or command text and parameters, rather than the rest of the line. This is commonly used to ignore options and commands which have variable parameters, but which are followed on the same line by other options and commands which you do not want to ignore.

Brackets ([ and ]) in a <string> have special meaning. Characters within a bracket are optional when parsing <string>. If the bracketed text is not present, <string> will still be parsed and translated correctly to the proper command.

Next Page

Previous Page

Go to Table of Contents

Go back to Devore Software & Consulting home page