From: Larry Evans (cppljevans_at_[hidden])
Date: 2007-09-26 13:20:03
On 09/26/07 11:22, Larry Evans wrote:
> On 09/26/07 10:36, Rene Rivera wrote:
[snip]
> Thanks *very much* for the clarification. I read about
> the difference between Boost.Build and Boost.Jam, but
> didn't really understand all that much. The keyword
> you used was *interface*. Somehow, it's got to be
> made clear to the user where that interface lies.
Maybe if the rule generated by the type rule:
The first way applies when your target rule should just produce a target
of specific type. In that case, a rule is already defined for you! When
you define a new type, Boost.Build automatically defines a corresponding
rule. The name of the rule is obtained from the name of the type, by
downcasing all letters
as described here:
http://www.boost.org/boost-build2/doc/html/bbv2/extending/rules.html
were described, in terms of the Boost.Jam statements used in the
body or the rule, things would be clearer. From an earlier
Volodya post:
http://article.gmane.org/gmane.comp.lib.boost.build/16245
I'm assuming this generated rule calls:
targets.main-target-alternative
It would probably be helpful if the interface between
Boost.Build and Boost.Jam were defined in terms of how
something in Boost.Build were translated into something
in Boost.Jam.