From: Phil Blundell <pb@pbcl.net>
To: openembedded-core@lists.openembedded.org
Subject: RSS difficulties
Date: Fri, 03 Feb 2017 11:10:59 +0000 [thread overview]
Message-ID: <1486120259.13882.26.camel@pbcl.net> (raw)
I'm having a few problems adapting our build setup to work with recipe
specific sysroots. More specifically, I am finding it difficult to get
the correct set of components installed into the recipe-sysroot in all
cases. In some cases I am getting too much (which causes build
failures if oe attempts to stage two things that install the same file)
and in other cases I am not getting enough.
Could somebody explain, ideally using only small words, how the set of
things to populate in the recipe-sysroot is determined? I assume it is
based on the task dependency graph somehow but I'm not quite sure which
relationships I ought to be looking at.
thanks
p.
next reply other threads:[~2017-02-03 11:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-03 11:10 Phil Blundell [this message]
2017-02-03 11:20 ` RSS difficulties Richard Purdie
2017-02-03 12:29 ` Phil Blundell
2017-02-06 13:42 ` Phil Blundell
2017-02-06 14:27 ` Richard Purdie
2017-02-06 14:44 ` Phil Blundell
2017-02-06 16:30 ` Phil Blundell
2017-02-06 16:55 ` Phil Blundell
2017-02-06 17:05 ` Burton, Ross
2017-02-06 20:54 ` Khem Raj
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=1486120259.13882.26.camel@pbcl.net \
--to=pb@pbcl.net \
--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