From: Alan Gutierrez (alan-jamboost_at_[hidden])
Date: 2004-12-29 13:51:27
* David Abrahams <dave_at_[hidden]> [2004-12-29 11:31]:
> Alan Gutierrez wrote:
> > I found it illuminating to read through the code in the kernel
> > directory.
> > Boost.Build v2 employs an implementation of polymorphic classes
> > that were built on top of the Jam syntax. It was really hard to
> > figure out what is going since a lot of the constructs are not
> > pure Jam, and not a description of a build process as one might
> > expect.
> > For some reason, finding the lines between Jam, Boost.Build, and
> > the toolsets makes me less anxious.
> I really hope that kind of low-level detail isn't neccessary for
> everyone. If it is, we really need to fix the documentation (well, I
> already know we need to fix the documentation).
I'm not going to volunteer to do this, I've bitten of more than
I can chew for the next five years, already, but...
I think a cookbook format is appropriate. It puts a developer's
mind at ease to read.
Title: Do This
Reason: You want to do this.
Solution: Do it like this.
Detail: The ins and outs, possible alternatives, and mistakes
made by folks doing this for the first time.
Which, when I think about it, I picked up Ant in a day or two
reading the Java Extreme Programming Cookbook.
Also, the low-level detail probably isn't necessary, but
somehow, it helps to know the strata of the architecutre.
Hmm.. Okay, once I saw that Boost.Build was polymorphic, and
that you'd assembled that from Jam primitives, I understood what
was going on a bit better, because I know how a systems pivots
when you add polymophism and encapsulation.
Without this understanding, I'm trying to map the concepts
directly to the Jam man page. Something was missing.
A page describing architecutre, and fundumental differences from
make would be a real leg up.
...I'll take notes, I don't know if it would be documentation,
but if it is at all useful, I'll submit a rule creation recipe
-- Alan Gutierrez - alan_at_[hidden]
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk