From: Steffen Sledz <sledz@dresearch.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Variable reference (was: Documentation update about machine conf files)
Date: Wed, 26 Aug 2009 09:39:55 +0200 [thread overview]
Message-ID: <4A94E6CB.6050604@dresearch.de> (raw)
In-Reply-To: <4A93FA79.80706@techworks.ie>
Christian Gagneraud wrote:
> Actually i was thinking as well to have a document presented as a matrix
> that will show quickly when and where this variables are intended to be
> used or not, ie:
>
> For each variable, there could be a:
> - one line documentation
> - default value
> - Used by (see below)
> - Used in (see below)
>
> For "Used by" and "Used in", it could be nice to specify yes, no or
> maybe (with default to no) for the following:
> - bitbake itself
> - <file>.bbclass
> - <package>.bb
> - <meta>.bb
> - <image>.bb
> - bitbake.conf
> - <distro>.conf
> - <machine>.conf
> - local.conf
> - any other interesting things...
>
> For the difference between used by and used in, here is an example:
> CMDLINE is used in <machine>.conf or local.conf, and is used by linux.inc
>
> I'm not (yet) familiar with bitbake and bbclass, but I guess that it is
> possible to extract all these information and generate say an xml file
> that can be in turn transformed into anything people like.
> ...
This sounds really good.
If this can done be automatically may be the best place for it could be a generated appendix to the user manual.
Steffen
prev parent reply other threads:[~2009-08-26 7:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-21 6:11 Variable reference (was: Documentation update about machine conf files) Steffen Sledz
2009-08-21 11:44 ` Holger Hans Peter Freyther
2009-08-24 15:00 ` Steffen Sledz
2009-08-25 2:03 ` Holger Hans Peter Freyther
2009-08-25 10:45 ` Steffen Sledz
2009-08-25 12:18 ` Holger Hans Peter Freyther
2009-08-25 14:51 ` Christian Gagneraud
2009-08-26 7:39 ` Steffen Sledz [this message]
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=4A94E6CB.6050604@dresearch.de \
--to=sledz@dresearch.de \
--cc=openembedded-devel@lists.openembedded.org \
/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