From: Rene Rivera (grafik666_at_[hidden])
Date: 2002-05-05 22:22:59
>> As for #3 & #5... Like I've mentioned before it's documentation that will
>> really helps the users at this point. And I aggree that it's needed to
>> alleviate the number of questions that always come up. Documenting the
>> individual toolsets is certainly good idea. But adding more jam code to
>> in a help system (even a minimal one) is more trouble than it's worth.
>> rather we put that same documentation into some, more user friendly, HTML
>OK, I agree. Let's do that, then.
>I suggest we make only one code change:
> Use the :J=" " trick to reconstitute single-item environment variables
>which may contain spaces. This applies especially to toolset config
>variables used to build Jam itself.
>The spaces in path names issue is easily solved and has been a major
>problem for users.
OK, that seems reasonable.
How's this for a todo list:
* Go through code and patch the " " variables.
* Create a template for documenting the variables for setting up building.
It should accomodate both general variables and toolset variables. Dave, I
suggest you do this, you are more familiar with the look-and-feel of Boost
* Go through code and identify and document each variable that is pertiment
to changing the behaviour of building. We should be able to split this task
among us to get it done faster.
Given the schedule of branching on the 8th can we get all that done? Or can
we keep adding documentation to the branch after the 8th, and just make sure
we have the code changes done?
By the way... I'll only have about 6 or so hours to spend on this through
Wednesday. So the sooner we get started the better.
-- grafik - Don't Assume Anything
-- rrivera_at_[hidden] - grafik_at_[hidden]
-- 102708583_at_icq - Grafik666_at_AIM - Grafik_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