A "multiplex rule" creates one transformer that takes all input artifacts with the matching input file tag and creates one or more artifacts (e.g. C++ linker). A "non-multiplex rule" creates one transformer per matching input file (e.g. C++ compiler).
Rule properties
\liProperty \li Type \li Default \li Description
\li multiplex \li bool \li false \li Determines if this is a multiplex rule.
\li inputs \li string list \li undefined \li File tags the input artifacts must match. All output artifacts will depend on all artifacts in the product with the given input file tags. Also these artifacts are available in the inputs variable of the prepare script.
\li usings \li string list \li undefined \li File tags the artifacts of product dependencies must match. Let there be a product foo which appears as
Depends {
name: "foo"
}
in the current product. All artifacts of foo that match the given file tags will appear in the inputs variable of the prepare script. Also, every output artifact of this rule will be dependent on those artifacts.
\li explicitlyDependsOn \li string list \li undefined \li Every artifact that matches the file tags in explicitlyDependsOn is added to the dependencies of every output node.
\li scanners \li string list \li undefined \li List of dependency scanner ids for this rule. The scanners are running just before the prepare script is executed.
\li prepare \li script \li undefined \li Script that prepares the commands to transform the inputs to outputs.