From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Yocto discussion list <yocto@yoctoproject.org>
Subject: should yocto ref manual variable glossary include bitbake variables?
Date: Tue, 17 Jun 2014 08:03:00 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.11.1406170800160.30459@localhost> (raw)
more pedantry -- reading both the bitbake user manual and the yocto
reference manual variable glossaries:
http://www.yoctoproject.org/docs/latest/bitbake-user-manual/bitbake-user-manual.html#ref-variables-glossary
http://www.yoctoproject.org/docs/latest/ref-manual/ref-manual.html#ref-variables-glos
and i notice, as a single example, the first mentions the variable
ASSUME_PROVIDED while the second does not. is this deliberate? is
there an explicit distinguishing of variables that belong to different
layers of the build system across the variable glossaries in different
manuals?
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
next reply other threads:[~2014-06-17 12:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-17 12:03 Robert P. J. Day [this message]
2014-06-17 13:52 ` should yocto ref manual variable glossary include bitbake variables? Rifenbark, Scott M
2014-06-18 9:28 ` Paul Eggleton
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=alpine.LFD.2.11.1406170800160.30459@localhost \
--to=rpjday@crashcourse.ca \
--cc=yocto@yoctoproject.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 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.