◄Up► ◄Contents► ◄Index► ◄Back►
─────Programmer's WorkBench─────────────────────────────────────────────────
 
     The Build:command rule defines a named command line for use in
     other Build rules.
 
     Syntax
 
     Build:[debug │ release] command <command> "<command_line>"
 
     debug             The command is used for debug builds.
 
     release           The command is used for release builds.
 
     command           A tag to indicate that this rule is a command.
 
     <command>         The name of the command for use in other build
                       rules. It is recommended that the command name
                       take the form:
 
                            <tool>[_<src>]_<dst>
 
                       The <tool> is the name of the first program used
                       in <command_line>, <src> is the extension of
                       source files for the command (if files of this
                       type appear in the file list), and <dst> is the
                       extension of output files from the command.
 
     <command_line>    The operating-system command line for the
                       command. You do not need to specify leading
                       spaces in the <command_line>; PWB automatically
                       indents the line as required by NMAKE.
 
     When you specify debug and release versions of <command>, PWB
     generates the following lines in the makefile.
 
          !IF $(DEBUG)
               <debug_command_line>
          !ELSE
               <release_command_line>
          !ENDIF
 
     If you specify only a debug or release command, PWB generates only
     the corresponding branch of the conditional. For unqualified
     commands (no 'debug' or 'release' tag), PWB inserts the command
     line into the appropriate description block or inference rule
     without conditional directives.
 
     To specify an NMAKE preprocessor directive in a Build command, you
     must separate the exclamation point (!) from the directive keyword
     with one or more spaces or tabs. For example, to specify a !MESSAGE
     directive, you must use '! MESSAGE'.
 
     The command-line strings can specify more than one line by using a
     newline specifier (\n) in the string. PWB does not automatically
     indent these embedded lines. Therefore, if the new line defines a
     command to be executed rather than an NMAKE directive, you must
     specify at least one space after the newline specifier.
 
     See
 
     ◄How PWB Creates a Project Makefile►
     ◄NMAKE Inline Files►
     ◄NMAKE Preprocessing Directives►
     ◄PWB Macro String Syntax►
                                    -♦-