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, 23 May 2014 13:45:08 +0800 [thread overview]
Message-ID: <006d01cf764a$2b710b80$82532280$@com> (raw)
In-Reply-To: <CAJTo0LbFKcv+riCYiNSJ0vOZHb4j6hi5hfLNpFya=pAkMyZ1kg@mail.gmail.com>
>>It's not opt-in: once a recipe is using doxygen.bbclass then it has a build dependency on doxygen-native and *will* generate documentation.
>>This is needless overhead if you don't intend to read the documentation.
>
> I think if you intend to read the documentation. Just inherit this class. If not. there is no need to inherit this class.
So you're suggesting that if a user wants documentation generated they should know what recipes they can add "inherit api-doc" to?
I'll repeat my proposal: every recipe that can generate doxygen documentation inherits a doxygen class, and that class can look at a distro-level variable along the likes of GENERATE_API_DOCS (which a hypothetical non-stub gtk-doc class can also respect).
[Zongchun] OK. Can you explain the details to use GENERATE_API_DOCS? I am not sure the meaning. Thanks.
next prev parent reply other threads:[~2014-05-23 5:44 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
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 [this message]
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='006d01cf764a$2b710b80$82532280$@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.