From: Zongchun YU <b40527@freescale.com>
To: "'Burton, Ross'" <ross.burton@intel.com>
Cc: 'OE-core' <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/2] Add api-doc class
Date: Fri, 16 May 2014 18:18:26 +0800 [thread overview]
Message-ID: <000501cf70f0$2f2d17a0$8d8746e0$@com> (raw)
In-Reply-To: <CAJTo0Lar8Hbc1Gsa3k631M697ZHDOufJ1k7ugTUU=AWXaHjMAQ@mail.gmail.com>
>>As this class is specific to doxygen, please call it doxygen.bbclass.
[Zongchun] I agree and will change it in the next patch.
>>Also I think this should be opt-in not forcibly enabled as not everyone would want API documentation to be generated.
[Zongchun] Yes. it is opt-in. the source code of packages should be written follow the rules of doxygen. If not. doxygen will not generate docs.
>>Pretty sure you'll want to run doxygen after do_compile in case the documentation is generated from files built at compile time. But don't most packages that use doxygen invoke it themselves? You're also not actually installing the documentation anywhere.
[Zongchun] doxygen just use source code(follow the rules of doxygen) of packages to generate docs. not use files built at compile time. Some packages may just need to fetch and patch the source code and then generate docs. the configure file of doxygen have options to specify the generated docs types and location. Whether install the docs may depend the packages.
next prev parent reply other threads:[~2014-05-16 10:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-16 7:45 [PATCH 2/2] Add api-doc class b40527
2014-05-16 9:39 ` Burton, Ross
2014-05-16 10:18 ` Zongchun YU [this message]
2014-05-16 10:34 ` Burton, Ross
2014-05-19 3:18 ` Zongchun YU
2014-05-19 9:46 ` Burton, Ross
2014-05-23 5:45 ` Zongchun YU
2014-05-23 9:37 ` Burton, Ross
-- strict thread matches above, loose matches on Subject: below --
2014-05-16 9:01 b40527
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='000501cf70f0$2f2d17a0$8d8746e0$@com' \
--to=b40527@freescale.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox