From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: BitBake developer list <bitbake-devel@lists.openembedded.org>
Subject: sadly, confused about recursive "recrdeptask" dependencies
Date: Sun, 10 Aug 2014 09:06:21 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.11.1408100858280.28636@localhost> (raw)
first, reading bitbake user manual and, in the section on dependency
task flags, i see nothing about the "recideptask" flag, which i only
tripped over recently while perusing oe-core:
distrodata.bbclass:do_distrodataall[recideptask] = "do_${BB_DEFAULT_TASK}"
distrodata.bbclass:do_checkpkgall[recideptask] = "do_${BB_DEFAULT_TASK}"
distrodata.bbclass:do_distro_checkall[recideptask] = "do_${BB_DEFAULT_TASK}"
distrodata.bbclass:do_checklicenseall[recideptask] = "do_${BB_DEFAULT_TASK}"
utility-tasks.bbclass:do_checkuriall[recideptask] = "do_${BB_DEFAULT_TASK}"
utility-tasks.bbclass:do_fetchall[recideptask] = "do_${BB_DEFAULT_TASK}"
should that be documented?
and as for "recrdeptask", well, i'm pretty sure i understand
build-time dependencies, and run-time dependencies, but does
recrdeptask correspond only to recursive run-time dependencies, or
*both* types of dependencies (as well as inter-task dependencies)? i'm
reading section 3.9.4 in the bitbake user manual, and i'm still
confused.
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-10 13:06 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.1408100858280.28636@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.