Thomas Witt wrote:
> Hi,
>
> Building the documentation for the 1.34.0 release is giving me a
> headache. Well actually it's not so much building as it is results.
> While I am reasonably confident that I have a working setup I don't
> feel that I can determine whether the built documentation is OK. For
> starters the build produces numerous warnings and errors from tools
> that are not reported as build errors. In short how do we do QA on
> the docs?
Good question: not much you can do except scan through and sift the wheat
from the chaff. I've posted some messages about the things that look like
errors.
I'm ignoring the doxygen warnings about stuff being undocumented, also the
warnings:
Cannot handle sectiondef with kind=private-attrib
Cannot handle sectiondef with kind=friend
Cannot handle sectiondef with kind=private-type
which appear to be doxygen related.
Also ignoring:
Cannot find class named 'std::unary_function'
Cannot find class named 'boost::program_options::command_line_parser'
Cannot find function named 'parse_config_file'
Reference to function 'boost::program_options::store' is ambiguous. Found:
Match in namespace ::
Match in namespace ::
Which have always been present, but I wish we could get rid of.
The main things to worry about IMO are warnings about duplicate or missing
linkend's as these translate to broken links in the final docs.
HTH, John.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Boost-docs mailing list
[email protected]
Unsubscribe and other administrative requests:
https://lists.sourceforge.net/lists/listinfo/boost-docs
