From: Darren Hart <dvhart@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: tocallaghan@meyn.net
Subject: Building core-image-rt - how to specify the rt kernel
Date: Thu, 05 Apr 2012 09:00:32 -0700 [thread overview]
Message-ID: <4F7DC1A0.9040607@linux.intel.com> (raw)
When building core-image-rt from the oe-core recipes-rt section, T
OCallaghan noticed he wasn't getting the linux-yocto-rt kernel. The
problem was that he was not setting the
PREFERRED_PROVIDER_virtual/kernel to linux-yocto-rt.
When I prepared the recipes-rt section, I wanted to be able to
automatically select the linux-yocto-rt kernel when building the
core-image-rt image. Unfortunately, the image recipe cannot set this
value as I understand it due to parse ordering and some fundamental
concepts about how the system works.
I documented the requirement to explicitly set this in the
recipes-rt/README, but that may not be an obvious place to look.
We have a couple of options here. We can try to improve the error
messages which are verbose and don't provide much direction for someone
new to the process:
ERROR: Multiple .bb files are due to be built which each provide
virtual/kernel
(/test_yocto/poky/meta/recipes-kernel/linux/linux-yocto-rt_3.2.bb
/test_yocto/poky/meta/recipes-kernel/linux/linux-yocto_3.2.bb).
This usually means one provides something the other doesn't and should.
We could document rt explicitly in the developer guide, although thus
far we haven't done much with these sorts of focused tactical issues in
the docs (I don't think). This also doesn't scale particularly well.
Finally, I could rip recipes-rt out of oe-core and maintain it in a
meta-rt layer whose layer.conf sets:
PREFERRED_PROVIDER_virtual/kernel ?= "linux-yocto-rt"
I'd appreciate thoughts on why one approach would be more appropriate
than another.
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
reply other threads:[~2012-04-05 16:10 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=4F7DC1A0.9040607@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=tocallaghan@meyn.net \
/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