Tokens
The following tokens are used in abstract commands:
OP <operation>– specifies the operation to perform. Values can be one of arch, bind, bind_so, comp, or comp_so.IF <filename>– specifies the input file to the compilation process. This may be a source file, an object file, or a response file which lists a number of object files.OF <filename>– specifies the output file of the compilation process. This may be an object file, a static library, a shared object (dynamic-linked library), or an executable program.XF <filename>– specifies a file containing a list of symbols which are to be exported from a shared object. This is specified under Windows and can be ignored for Linux platforms.FL <flags…>– specifies one or more flags to be passed through to the compiler. This list is terminated by a token consisting of a double colon. These flags will usually be specified by the user via a preference.IN <include dir>– specifies the name of an additional directory in which the compiler should search for header files. Since a single additional directory is specified, this is not a list token.LB <libraries…>– specifies one or more libraries to be passed to the linker. The libraries may be specified by the user via a preference, by Riverbed Modeler, or both.- VM – specifies that the script or compiler print to standard output the exact compilation or linking command (including flags) it sent to the operating system. This is useful for gathering information when you have trouble compiling or linking code.
TA <target>– specifies the target architecture for compilation.<target>can be32bitor64bit.
Note: Printing the command typically causes the top-level compilation or linking operation to fail. Therefore, use this token only when performing diagnostics or debugging.