<string>=<WL32 option>

Translate <string> to the listed WL32 option. This command is most useful for a linker response file that has an option directly corresponding to a WL32 option, but with a different syntax. Here are a few common examples:

STACK=/st:

VERBOSE=/i

/nod=/nd

Multiple WL32 option morphing commands are supported by WL32.

<filename>=+<WL32 option>

Turn on <WL32 option> if <filename> is encountered in the link file as an object module or library. A path specification is not necessary for <filename>.

<filename>=+OBJ:<OBJ filename>

This command is the same as OBJAPPEND, except linking of <OBJ filename> is conditional based upon the presence of <filename>. Useful for linking in a path object module if a library is present. If no file extension is given for <OBJfilename>, the default is used: .OBJ.

<environment variable setting>=@<linkfile>

Process <linkfile> only if <environment variable setting> is properly set. Multiple <linkfile> commands are processed in order listed in the .DEF file following the initial command line, link file, and DEF file processing. This command is potentially very powerful and allows you to structure and control the link process almost entirely through the environment variable settings.

Example:

COW=MOO=@MILK.LNK

In this example, WL32 will process MILK.LNK if the environment variable COW is set to MOO. Extraneous letters following the MOO setting will also match, i.e., SET COW=MOON will trigger MILK.LNK link file processing. Remember that the environment variables are case sensitive. SET COW=moo will not trigger MILK.LNK file processing.

This command is most useful for FREEFORMAT link file processing, since it would be difficult to optionally process files and libraries in the positional link file format.

Next Page

Previous Page

Go to Table of Contents

Go back to Devore Software & Consulting home page