boost/build
2
0
Fork 0
mirror of https://github.com/boostorg/build.git synced 2026-02-18 01:52:17 +00:00
Code Issues Projects Releases Wiki Activity

Add/clarify comments.

Browse Source 
[SVN r18496]
This commit is contained in:
Vladimir Prus
2003-05-22 11:50:10 +00:00
parent 48b5b18d85
commit 9dda3d8f84
4 changed files with 22 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
new/builtin.jam
View File

@@ -621,10 +621,14 @@ rule link-action ( targets + : sources * : action-name : properties * )
class link-action : action ;
rule linking-generator ( id composing ? : source-types + : target-types + :
rule linking-generator ( id
composing ? : # Specify if generator is composing. The generator will be
# composing if non-empty string is passed, or parameter is
# not given. To make generator non-composing, pass empty
# string ("")
source-types + : target-types + :
requirements * )
{
# If composing is not specified, set it to true, which is "false" in Jam.
composing ?= true ;
generator.__init__ $(id) $(composing) : $(source-types) : $(target-types) :
$(requirements) ;

6
new/generators.jam
View File

@@ -287,7 +287,11 @@ rule generator (
multiple = ;
}
# We don't run composing generators which are not given a name.
# We don't run composing generators if no name is specified. The reason
# is that composing generator combines several targets, which can have
# different names, and it cannot decide which name to give for produced
# target. Therefore, the name must be passed.
#
# This in effect, means that composing generators are runnable only
# at top-level of transofrmation graph, or if name is passed explicitly.
# Thus, we dissallow composing generators in the middle. For example, the

6
v2/build/generators.jam
View File

@@ -287,7 +287,11 @@ rule generator (
multiple = ;
}
# We don't run composing generators which are not given a name.
# We don't run composing generators if no name is specified. The reason
# is that composing generator combines several targets, which can have
# different names, and it cannot decide which name to give for produced
# target. Therefore, the name must be passed.
#
# This in effect, means that composing generators are runnable only
# at top-level of transofrmation graph, or if name is passed explicitly.
# Thus, we dissallow composing generators in the middle. For example, the

8
v2/tools/builtin.jam
View File

@@ -621,10 +621,14 @@ rule link-action ( targets + : sources * : action-name : properties * )
class link-action : action ;
rule linking-generator ( id composing ? : source-types + : target-types + :
rule linking-generator ( id
composing ? : # Specify if generator is composing. The generator will be
# composing if non-empty string is passed, or parameter is
# not given. To make generator non-composing, pass empty
# string ("")
source-types + : target-types + :
requirements * )
{
# If composing is not specified, set it to true, which is "false" in Jam.
composing ?= true ;
generator.__init__ $(id) $(composing) : $(source-types) : $(target-types) :
$(requirements) ;