Lines Matching refs:I
17 B<SUBDIRS=> I<dir> ...
19 B<PROGRAMS=> I<name> ...
21 B<LIBS=> I<name> ...
23 B<MODULES=> I<name> ...
25 B<SCRIPTS=> I<name> ...
27 B<DEPEND[>I<items>B<]=> I<otheritem> ...
29 B<GENERATE[>I<item>B<]=> I<generator> I<generator-args> ...
31 B<SOURCE[>I<item>B<]=> I<file> ...
33 B<SHARED_SOURCE[>I<item>B<]=> I<file> ...
35 B<DEFINE[>I<items>B<]=> I<name>[B<=>I<value>] ...
37 B<INCLUDE[>I<items>B<]=> I<dir> ...
39 B<$>I<VARIABLE>B<=>I<value>
123 =item B<I<KEYWORD>> B<=> I<value> ...
125 =item B<I<KEYWORD>[>I<items>B<]> B<=> I<value> ...
129 Every B<I<KEYWORD>> represents some particular type of information.
175 =item B<I<KEYWORD>{> I<attrib> | I<attrib>B<=>I<attrib-value> [,...]B<}>
176 B<=> I<value> ...
178 =item B<I<KEYWORD>[>I<items>B<]{> I<attrib> | I<attrib>B<=>I<attrib-value>
179 [,...]B<}> B<=> I<value> ...
262 =item B<$>I<NAME> B<=> I<value>
268 I<variables are expanded into their values before the value they are
271 I<Variable assignment values are not tokenized.>
277 =item B<$>I<NAME> or B<${>I<NAME>B<}>
282 =item B<${>I<NAME>B</>I<str>B</>I<subst>B<}>
285 value, modified by replacing all occurrences of I<str> with I<subst>.
361 =item B<SUBDIRS=> I<dir> ...
367 =item B<PROGRAMS=> I<name> ...
380 =item B<LIBS=> I<name> ...
402 =item B<MODULES=> I<name>
415 =item B<SCRIPTS=> I<name>
436 =item B<DEPEND[>I<items>B<]> B<=> I<file> ...
438 Collects dependencies, where I<items> depend on the given I<file>s.
440 As a special case, the I<items> may be empty, for which the build file
441 generators should make the whole build depend on the given I<file>s,
442 rather than the specific I<items>.
444 The I<items> may be any program, library, module, script, or any
447 The I<items> may also be literal build file targets. Those are
464 B<DEPEND> is a bit more involving when used with I<item>s that are
467 =item B<GENERATE[>I<item>B<]> B<=> I<generator> I<generator-arg> ...
469 This specifies that the I<item> is generated using the I<generator>
470 with the I<generator-arg>s as arguments, plus the name of the output
473 The build file generators must be able to recognise the I<generator>.
475 execute them to generate the I<item>, and files ending in C<.in>,
477 I<item> (in other words, we use the exact same style of
480 For I<generator>s where this is applicable, any B<INCLUDE> statement
481 for the same I<item> will be given to the I<generator> as its
484 Likewise, For I<generator>s where this is applicable, any B<DEPEND>
485 statement for the same I<item> will be given to the I<generator> as an
493 as an B<INCLUDE> statement for the directory where the I<file> is
502 different I<file> syntax, that looks like this:
504 B<DEPEND[>I<items>B<]> B<=> I<dir>|I<module>
506 The I<module> must be specified in a way that makes sense for the generator.
516 =item B<SOURCE[>I<item>B<]> B<=> I<file> ...
518 Collects filenames that will be used as source files for I<item>.
520 The I<item> must be a singular item, and may be any program, library,
525 used directly when building I<item> instead of relying on library
539 =item B<SHARED_SOURCE[>I<item>B<]> B<=> I<file> ...
541 Collects filenames that will be used as source files for I<item>.
543 The I<item> must be a singular item, and may be any library or module
551 =item B<DEFINE[>I<items>B<]> B<=> I<name>[B<=>I<value>] ...
553 Collects I<name> / I<value> pairs (or just I<name> with no defined
554 value if no I<value> is given) associated with I<items>.
560 =item B<INCLUDE[>I<items>B<]> B<=> I<dir> ...
563 I<items> components (object files and whatever else). This is used at
605 like this, means that if I<both> C<libfoo.a> and C<libmandatory.a>
641 Any F<build.info> statement of the form B<I<KEYWORD>>=I<values>, with
646 Any F<build.info> statement of the form B<I<KEYWORD>[>I<items>B<]=>I<values>,
