Lines Matching full:statement

81 Any time a directory or file is expected in a statement value, Unix
118 With the exception of variables and conditions, the general statement
131 The first form (sometimes called "plain statement") is used to specify
146 The second form (sometimes called "indexed statement") is used to
163 For any indexed statement for which the items haven't been specified
164 through any plain statement, or where the items exists but the indexed
165 statement does not apply, the value is simply ignored by the build
168 =head3 Statement attributes
216 Statement values are normally split into a list of tokens, separated
266 These variables can then be used as part of any statement value or
267 indexed statement item.  This should be used with some care, as
291 Most of the statement values are accumulated globally from all the
293 F<build.info> variables and B<SUBDIRS> statement, for which the scope
372 programs given in such a statement.  For example:
394 libraries given in such a statement.  For example:
407 modules given in such a statement.  For example:
422 scripts given in such a statement.  For example:
454 individual dependency in such a statement.  For example:
470 For I<generator>s where this is applicable, any B<INCLUDE> statement
472 inclusion directories.  Likewise, any B<DEPEND> statement for the same
496 individual dependency in such a statement.  For example:
606 =item "plain statement"
608 Any F<build.info> statement of the form B<I<KEYWORD>>=I<values>, with
611 =item "indexed statement"
613 Any F<build.info> statement of the form B<I<KEYWORD>[>I<items>B<]=>I<values>,