From: Vladimir Prus (ghost_at_[hidden])
Date: 2004-01-23 08:27:18
Zbynek Winkler wrote:
> >>I'm finally taking some time to use Boost.Buildv2 for some of my
> >> projects. I do not have much v1 experience (except for making boost test
> >> Jamfiles), but I thought it could be a good idea to go directly for v2
> >> (is it ?)
> I did and so far I am happy :-)
> > Why did you wonder what directories bjam invocation depends on? I'm just
> > trying to figure out what exactly should be put to docs.
> My guess would be that we wonder about what the tools we use do because
> after all - we all programmers, right? :-) I ask myself - do I want to use
> something the does some "magic"? No. Because what happens when I am stuck
> with it and it stops doing the "right" kind of magic?
I see. Maybe, the beginning of "Reference" section should start with:
Boost.Build consists of Boost.Jam binary -- which is a build tool with it's
own interpreted language -- and Boost.Build itself, which is written in
Boost.Jam language. On startup, bjam loads Boost.Build modules as described
in <link>. After that, Boost.Build starts to loading files describing project
-- Jamfiles, creating targets along the way. After that the targets are
Does this clarify anything?
> >>It would be a good time to state that the jam files in this directory
> >>hierarchy are well commented and are the ultimate place to go to when you
> >>don't understand something with Boost.Build.
> > Cool! I'll sure add this too ;-)
> It took me a quite time to find that out. It would be definitively helpful
> to know.
Ok, I'll mention this right in the beginning of "Reference" section, after
noting that on-line help system exists.
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