Robert Ramey wrote:
Actually what I would like to do is the following:
a) do an SVN update of my BoostRelease directory. This is what I do now. Works great. So I have on my machine the whole "next release"
b) Then I want to be able to invoke something like bjam " build documentation" from the BoostRelease directory. I think I can do this and in fact I think I have done this - I just forgot the procedure.
You are supposed to only need to: cd <boost-root>/doc bjam But this is assuming you have set up all the dependent tools you need to build DocBook docs.
This would give me the following:
a) The documentation on my local system for the "next release"
b) the build process should much simpler and more up to date then downloading a whole new zip. The build would only have to build those components which have changed.
c) I could choose which kind of documentation I wanted html or pdf or (maybe someday) windows help file
Building PDF docs is complicated by needing to have a specific PDF generator software which is commercial, IIRC. I heven't tried building PDF so someone else will have to answer as to how to do it. -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org (msn) - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim,yahoo,skype,efnet,gmail