From: Michael Stevens (Michael.Stevens_at_[hidden])
Date: 2004-06-08 03:00:11
On Monday 07 June 2004 09:37, Vladimir Prus wrote:
> > Should new toolset documentation be in Boostbook source format?
> Yes, Boostbook is now the official documentation format.
> I wonder how toolset docs are to be related with online help. After all,
> the original intention was that "bjam --help msvc.init" could produce help
> for the msvc module.... OTOH, it's not possible to produce docbook output
> right now and we still need docs, so I guess you can go ahead.
Ah I see you were intending the toolset help to work via the --help mechanism.
I will put together a bookbook source for for the intel-linux toolset and see
how it works out.
> > While setting up Boostbook I stumbled across a bug. The 'doc/catalog.xml'
> > file is not overwritten once it has already been created. Therefore
> > changing DTD XSL or directory location specification in user-config (or
> > environment variables) is ineffective once bjam has been run once.
> This is very unfurtunate thing. The story is: it was reported as bug. I've
> found that some other jam variant has a builtin IFUSED which could help.
> Doug asked how he can see implementation of this builting. I've looked at
> the code and could not find it. The original author said to me he might
> have removed the builtin, but has not yet replied to a question asking if
> he found a better way.
OK sounds complicated! I was assuming the mechanism was similar to the used to
generate response files for some toolset. It may also be worth considering
the current system also seems to have the disadvantage that need write access
to the source directory.
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