On Monday 24 January 2005 15:34, Douglas Gregor wrote: > On Jan 24, 2005, at 2:49 AM, Vladimir Prus wrote: > > On Saturday 22 January 2005 19:44, Eric Niebler wrote: > >> David Abrahams wrote: > >>> Aleksey Gurtovoy <[EMAIL PROTECTED]> writes: > >>>> Our nightly documentation build failed with the following > >>>> diagnostics: > >>> > >>> I took a wild guess and checked in a fix. Let me know if it works. > >> > >> Doesn't work for me: > > > > It looks like Doug has committed a fix for this. Thanks, Doug! > > I still couldn't fix that bleepin' catalog.xml problem, though :( At > least now it's in "bin.v2", so wiping out the state of bjam gets rid of > it instead of leaving it around in the source directory.
Still have no nice solution to that problem. > > > OTOH, the 'boostbook.py' Boost.Build test is still broken, as I > > reported on > > boost-docs list on Friday. > > Hmmm, which version of Doxygen are you using? I've been looking at the > output of Doxygen 1.4.0, and it seems that they've changed the XML > output again (for the worse). It used to be that one could follow > <innerclass> elements from a file to get to the members of that file, > but no more! I really wish they would either (a) get it right, or (b) > stop messing with it. "Doxygen version 1.4.0", I'm told :-( Maybe you can express your opinion on the doxygen mailing list? - Volodya ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ Boost-docs mailing list [email protected] Unsubscribe and other administrative requests: https://lists.sourceforge.net/lists/listinfo/boost-docs
