chri...@natinst.com writes:
I am having trouble figuring out how to deal with actions that produce
multiple targets. For example, if I want to make a "Browser
Database" with
I've been playing with this idea: create a NOTFILE target that
represents the "bundle" of all the generated files, then make each
generated file depend on the bundle target. The rule generating the
bundle would be something like CcSBR, whose actions use the right
cmd-line arguments; the actions for the .obj and .sbr files would be
no-ops.
I haven't done very complicated things with this; in
particular, I don't know how to write the rules so the .sbr file is
not generated if the build targets don't require it. If you could have
a variable controlling the generation, you could do
if $GENERATE_SBR
{
RuleWithSBRs
}
else
{
RuleWithoutSBRs
}
but that's not the best interface.
Has anyone hacked Jam to export the list of build targets as a
variable?
- - Sriram