Lines Matching full:transformation

1249 The application of suffix-transformation rules. (See chapter 3)
1628 .xH 2 Transformation Rules
1649 ability comes from something known as a transformation rule. A
1650 transformation rule specifies how to change a file with one suffix
1653 A transformation rule looks much like a dependency line, except the
1670 to the transformation rule.
1678 transformation rules (and suffixes) are defined there, and I refer you
1683 There are several things to note about the transformation rule given
1698 variable. Almost all of the transformation rules in the system
1722 The transformation rule I gave above takes the place of the 6 lines\**
1743 transformation rule is the target comes to depend on the implied
1798 sources for a target using transformation rules.
1800 enough, limited to the ones that have been defined (a transformation
1807 the source of a transformation. Once a suffix has been defined, the
1812 want. (Previously-defined transformation rules will be automatically
1822 Since a transformation exists from
1830 The search for a transformation starts from the suffix of the target
1834 found. At that point, one or more transformation rules will have been
1900 At this point, it has defined a transformation path as follows:
1908 and applies the transformation rules accordingly. For completeness,
1910 three-step transformation, this is what PMake printed for the rest of
2073 Any attributes given as sources for a transformation rule are applied
2074 to the target of the transformation rule when the rule is applied.
2764 How can you still use transformation rules to make your life easier
2851 it will be found using transformation rules if it isn't given. This is because
2853 is the null suffix by default and a transformation exists from
2873 down enormously because of PMake's attempts to apply transformation
2933 taken with the transformation rules, as follows:
2937 The transformation from the \fImember\fP's suffix to the
3774 .Gp "transformation rule"