<html><head></head><body><div>On Tue, 2016-08-02 at 17:56 +0100, Burton, Ross wrote:</div><blockquote type="cite"><div dir="ltr"><div class="gmail_extra">Hi,</div><div class="gmail_extra"><br><div class="gmail_quote">On 27 July 2016 at 06:02, Dengke Du <span dir="ltr"><<a href="mailto:dengke.du@windriver.com" target="_blank">dengke.du@windriver.com</a>></span> wrote:<br><blockquote type="cite"><div>When using '<span>perf</span> help <subcommand>', it can't find 'man' command and pages for<br>
<span>perf</span>.<br>
The <span>perf</span> man pages depends on the xmlto-native and asciidoc-native, so we just<br>
need to add the two packages to the DEPENDS variable and add 'man'to<br>
RDEPENDS_perf-doc.</div><br></blockquote></div><br>Whilst I like the idea of supporting more documentation, and have long wanted to integrate doxygen/gtk-doc/etc into Yocto for building SDKs with API documentation, I'm not sure we should be making random packages depend on tooling to always generate documentation.</div><div class="gmail_extra"><br></div><div>What do people think of a distro feature / global environment variable for "recipe should build the documentation"? For perf this would mean adding asciidoc so it can build the man pages, for GLib it would mean depending on gtk-doc so the API docs can be generated, and so on. But if they're not needed then they can be disabled to improve build speeds.</div></div>
</blockquote><div><br></div><div>I like the idea. I've had a similar one in mind for a while now as it would be a nice feature to be able to provide the documentation for an image as an output of the system.</div><div><br></div><div>Regards,</div><div><br></div><div>Joshua</div></body></html>