From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: BitBake developer list <bitbake-devel@lists.openembedded.org>
Subject: some (admittedly dopey) questions about dependencies
Date: Mon, 11 Aug 2014 15:12:04 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.11.1408111504230.9626@localhost> (raw)
digging thru bitbake manual, as well as the code in runqueue.py, so
some questions about the niggling details regarding dependencies.
first, what does "recrdeptask" stand for? yes, i realize it refers
to "recursive" dependencies, but what's with the leading "recr"? does
that represent recursive "recr" deptasks, or recursive "rec"
rdeptasks? or what? knowing what it's short for always helps.
next, i see five types of dependencies being processed in that code
in the prepare() method:
* tdepends: internal task dependencies (based on addtask)
* deptask: build-time dependencies
* rdeptask: run-time dependencies
* idepends: inter-task dependencies
* recrdeptask: recursive dependencies
and i am still unclear on what recrdeptask represents: the comment in
that file reads:
# e.g. do_sometask[recrdeptask] = "do_someothertask"
# (makes sure sometask runs after someothertask of all DEPENDS,
RDEPENDS and intertask dependencies, recursively)
is that description correct? how does it relate to inter-task
dependencies, which explicitly list the name of the other task?
anyway, if someone can clarify that, that would be ducky.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
reply other threads:[~2014-08-11 19:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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.1408111504230.9626@localhost \
--to=rpjday@crashcourse.ca \
--cc=bitbake-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 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.