From: Vladimir Prus (ghost_at_[hidden])
Date: 2008-02-21 03:44:15
Jurko GospodnetiÄ wrote:
> Hi Alex
>> Yeah, I think it's a bug in my understanding of bjam. Bjam takes time to understand when you
>> need to do something not trivial.
> Yup... :-) The problem is a general lack of shrink-wrapped
> documentation... :-)) Well, the documentation is mostly there, but in
> almost all border-line cases it is lacking... :-)
> That said, the plan is to work on the documentation for the next
> milestone, but somehow no one has started to organize this effort... :-))
> Volodya... any chance of you organizing the effort? I'd be happy to
> chip in and do some of the work, but I do not feel up to the task of
> working alone on it or trying to prepare a project overview for
I think the list of issues assigned for the docs milestone can
be a good approximation. I probably can look at them, and create
a wiki page describing the critical issues with the documentation
I know, and ask for feedback of users. Does that sound good?
> Or should we wait for the first Python port alpha release to
> become available?
It's independent, mostly. While the extender's manual will have to
be adjust for Python, most user-level docs and context will remain
> I guess I first need to find out how to set up the build for the
> documentation on my local machine... :-))) Will try to do that this
> weekend... :-))
Feel free to poke me if you run into problems (including poking over ICQ
or Skype or IRC (#boost on freenode)).
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