Subject: Re: [Boost-build] Documentation toolchain, ease of use
From: Daniel James (dnljms_at_[hidden])
Date: 2011-02-04 14:04:17
On 4 February 2011 18:33, Steven Watanabe <watanabesj_at_[hidden]> wrote:
> On 2/4/2011 10:12 AM, Daniel James wrote:
>> I recently changed fop so that if initialized a second time it
>> overwrites the initial settings. Glancing at the other tools, it looks
>> like if they're initialized a second time it's ignored (which seems
>> wrong to me).
> Overwriting the settings is potentially
> dangerous if any targets are created in
> between. I'd rather have it be an error.
> using xxx ; does appear in quite a few
> Jamfiles, so changing it to overwrite the
> settings with whatever would be found
> by default would be a bad idea, as it
> would almost certainly break anyone trying
> to build the documentation on windows.
Vladimir suggested I remove the reinitialisation check so that local
configuration can overwrite global - which is a reasonable
requirement. Maybe it should ignore reinitialisation without values,
and be an error if it's reinitialised with values after being used for
anything else - assuming no actions are performed by configuration
files, that we can detect use and it isn't too hairy to implement.
> To make things work with no user configuration,
> I need a way to say "Make sure the tool is
> initialized. I don't care how." and initializing
> with no arguments seemed like the most natural
This is really going to need a warning (or error) for any Jamfiles
which don't have the necessary using directives (or whatever), even if
they are already configured. Is that possible?
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