From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: "bitbake -c fetchall" doesn't process EXTRA_IMAGEDEPENDS
Date: Tue, 29 Jan 2013 04:41:20 -0500 (EST) [thread overview]
Message-ID: <alpine.DEB.2.02.1301290439030.12651@oneiric> (raw)
back in november, i whined thusly:
http://lists.linuxtogo.org/pipermail/openembedded-core/2012-November/031997.html
is this the *intended* behaviour? since it seems that if i do a
"bitbake -c fetchall", i should expect that i now have *all* software
related to my target, and that's clearly not the case here.
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:[~2013-01-29 9:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-29 9:41 Robert P. J. Day [this message]
2013-01-30 13:02 ` "bitbake -c fetchall" doesn't process EXTRA_IMAGEDEPENDS Richard Purdie
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.DEB.2.02.1301290439030.12651@oneiric \
--to=rpjday@crashcourse.ca \
--cc=openembedded-core@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