Matias Capeletto wrote: > Yes, and there are tons of warning and errors in library docs. > Two things. > First, I really think we should treat .qbk files with the same > diligence we treat our source code. That means taking the time to > eliminated all the warnings. A general build, must be a clean build to > be successful.
Also agree 100%. Personally I make sure that my quickbook files build clean from within their own sub-directory, but the whole slew of messages - and the long build time - from the doc directory is a real obstacle. I'm not sure how we solve it though: I believe that most of the messages are Doxygen related, and I know nothing about that :-( > Second, Is there a way in which each library generate a .xml and a > script join them together to build the general docs? That's what happens now isn't it? doc/Jamfile.v2 builds each lib's docs to XML and then the master xml file just includes all those separate libraries in one big master XML file that gets rendered to HTML. John. ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Boost-docs mailing list [email protected] Unsubscribe and other administrative requests: https://lists.sourceforge.net/lists/listinfo/boost-docs
