diff options
author | Richard Levitte <levitte@openssl.org> | 2020-02-26 14:30:38 +0100 |
---|---|---|
committer | Richard Levitte <levitte@openssl.org> | 2020-03-02 03:34:29 +0100 |
commit | ad5be194c6b08e89f9a6e2a78b85ff19a3c40d40 (patch) | |
tree | f0cbdff589345c712e38df094f76b21810c7dfa2 /doc/internal/man7 | |
parent | 2888fc1590ad31633be7a99e7288dcecd35e800c (diff) |
build.info: Make it possible to have more than one item in KEYWORD[]
So far, the "index" part of KEYWORD[whatever] could only handle one
item. There are cases, however, where we want to add the exact same
value to multiple items. This is especially helpful if a variable
that may have multi-item values are used in the "index" part.
Reviewed-by: Tomas Mraz <tmraz@fedoraproject.org>
(Merged from https://github.com/openssl/openssl/pull/11185)
Diffstat (limited to 'doc/internal/man7')
-rw-r--r-- | doc/internal/man7/build.info.pod | 40 |
1 files changed, 23 insertions, 17 deletions
diff --git a/doc/internal/man7/build.info.pod b/doc/internal/man7/build.info.pod index 2be709f770..c2020a432f 100644 --- a/doc/internal/man7/build.info.pod +++ b/doc/internal/man7/build.info.pod @@ -24,7 +24,7 @@ B<MODULES=> I<name> ... B<SCRIPTS=> I<name> ... -B<DEPEND[>I<item>B<]=> I<otheritem> ... +B<DEPEND[>I<items>B<]=> I<otheritem> ... B<GENERATE[>I<item>B<]=> I<generator> I<generator-args> ... @@ -32,9 +32,9 @@ B<SOURCE[>I<item>B<]=> I<file> ... B<SHARED_SOURCE[>I<item>B<]=> I<file> ... -B<DEFINE[>I<item>B<]=> I<name>[B<=>I<value>] ... +B<DEFINE[>I<items>B<]=> I<name>[B<=>I<value>] ... -B<INCLUDE[>I<item>B<]=> I<dir> ... +B<INCLUDE[>I<items>B<]=> I<dir> ... B<$>I<VARIABLE>B<=>I<value> @@ -122,7 +122,7 @@ syntax is one of: =item B<I<KEYWORD>> B<=> I<value> ... -=item B<I<KEYWORD>[>I<item>B<]> B<=> I<value> ... +=item B<I<KEYWORD>[>I<items>B<]> B<=> I<value> ... =back @@ -154,8 +154,14 @@ F<foo.c> and F<details.c>, and that it depends on the library C<libcookie> (in other words, the library will be included when linking that program together). -For any indexed statement for which the item hasn't been specified -through any plain statement, or where the item exists but the indexed +Multiple space separated items are allowed too: + + SOURCE[foo]=foo.c + SOURCE[details]=details.c + DEPEND[foo details]=libcookie + +For any indexed statement for which the items haven't been specified +through any plain statement, or where the items exists but the indexed statement does not apply, the value is simply ignored by the build file generators. @@ -169,7 +175,7 @@ variations on how they are treated. =item B<I<KEYWORD>{> I<attrib> | I<attrib>B<=>I<attrib-value> [,...]B<}> B<=> I<value> ... -=item B<I<KEYWORD>[>I<item>B<]{> I<attrib> | I<attrib>B<=>I<attrib-value> +=item B<I<KEYWORD>[>I<items>B<]{> I<attrib> | I<attrib>B<=>I<attrib-value> [,...]B<}> B<=> I<value> ... =back @@ -411,15 +417,15 @@ C<noinst>, while the script C<bar> will. =over 4 -=item B<DEPEND[>I<item>B<]> B<=> I<file> ... +=item B<DEPEND[>I<items>B<]> B<=> I<file> ... -Collects dependencies, where I<item> depends on the given I<file>s. +Collects dependencies, where I<items> depend on the given I<file>s. -As a special case, the I<item> may be empty, for which the build file +As a special case, the I<items> may be empty, for which the build file generators should make the whole build depend on the given I<file>s, -rather than some specific I<item>. +rather than the specific I<items>. -The I<item> may be any program, library, module, script, or any +The I<items> may be any program, library, module, script, or any filename used as a value anywhere. B<DEPEND> statements may have attributes, which apply to each @@ -473,19 +479,19 @@ given with B<LIBS> or B<MODULES>. For libraries, the given filenames are only used for their shared form, so if the item is a library name ending with C<.a>, the filenames will be ignored. -=item B<DEFINE[>I<item>B<]> B<=> I<name>[B<=>I<value>] ... +=item B<DEFINE[>I<items>B<]> B<=> I<name>[B<=>I<value>] ... Collects I<name> / I<value> pairs (or just I<name> with no defined -value if no I<value> is given) associated with I<item>. +value if no I<value> is given) associated with I<items>. The build file generators will decide what to do with them. For example, these pairs should become C macro definitions whenever a C<.c> file is built into an object file. -=item B<INCLUDE[>I<item>B<]> B<=> I<dir> ... +=item B<INCLUDE[>I<items>B<]> B<=> I<dir> ... Collects inclusion directories that will be used when building the -I<item> components (object files and whatever else). This is used at +I<items> components (object files and whatever else). This is used at the discretion of the build file generators. =back @@ -568,7 +574,7 @@ the exception of conditional statements and variable assignments. =item "indexed statement" -Any F<build.info> statement of the form B<I<KEYWORD>[>I<item>B<]=>I<values>, +Any F<build.info> statement of the form B<I<KEYWORD>[>I<items>B<]=>I<values>, with the exception of conditional statements. =item "intermediate file" |