From: Dean Michael Berris (mikhailberis_at_[hidden])
Date: 2007-01-15 06:18:02
It might just be me, but I think it's pretty obvious that we need to
generate documentation that's easily accessible and easily editable by
the community at large. I see there's
-- which one should be used, and is there an effort to actually start
generating (more) documentation about Boost.Build and Boost.Jam ?
I feel there's nothing wrong with using quickbook+boostbook to
document Boost.Jam and Boost.Build, but downloading the Boost
Distribution and having to wade through how to actually build Boost
and the other tools causes somewhat a circular dependency problem --
and can be considered a serious barrier to entry. Not to mention that
it's pretty complex to develop documentation collaboratively in this
method, where it takes a considerable while between writing and
copy-editing and eventual release (and even the full cycle).
Though some of us have been successful and able to figure out how
Boost.Build and Boost.Jam (and even quickbook+boostbook) work, some of
us (me included) have very short attention spans and wouldn't want to
go through all that again just to explain it to someone else.
So if there isn't already an effort, I would like to volunteer some of
my time going over what we already have and collate information and
have it consolidated somewhere convenient.
Now the question is, where should I start?
-- Dean Michael C. Berris http://cplusplus-soup.blogspot.com/ mikhailberis AT gmail DOT com +63 928 7291459
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