From: Tom Zanussi <tom.zanussi@intel.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: Yocto discussion list <yocto@yoctoproject.org>
Subject: Re: working my way through the kernel hands-on labs finally
Date: Mon, 08 Apr 2013 19:58:47 -0500 [thread overview]
Message-ID: <1365469127.17697.70.camel@empanada> (raw)
In-Reply-To: <alpine.DEB.2.02.1304081135020.23038@oneiric>
On Mon, 2013-04-08 at 11:41 -0400, Robert P. J. Day wrote:
> finally have the time to work my way through the ELC 2013 hands on
> kernel labs described here:
>
> https://www.yoctoproject.org/tools-resources/presentations/working-kernel
>
> since i'll almost certainly use some of them in my next yocto course,
> so the occasional question for anyone who's already been down this
> road. start with lab 1.
>
> the doc mentions including the meta-yocto and meta-yocto-bsp layers
> -- are those strictly necessary? the layer.conf definition file for
> the lab1 layer doesn't list those layers as dependencies. what will
> happen if i leave them out? what's the policy on explicitly listing
> dependencies on those two layers in a new layer?
>
The bblayers.conf for the labs is just the bblayers.conf that gets
generated the first time you source oe-init-build-env in poky, which is
what the lab is based on. You shouldn't need those layers - the BSPs
should work fine outside of poky, but since this is a yocto lab and it
uses poky, there's no need to make a point of removing them - actually,
I haven't tried removing those layers - meta-yocto-bsp could certainly
be removed since it's all machine-specific to existing BSPs, but it's
easy enough to remove them and see...
> also, just doing a basic fetch for lab1 produces:
>
> ERROR: QA Issue:
> /home/rpjday/yocto/k_lab/layers/meta-lab1-qemux86/recipes-kernel/linux/linux_3.0.18.bb:
> Variable FILES is set as not being package specific, please fix this.
>
> is that deliberate? something that will be resolved later in the
> lab as part of an exercise? just curious.
>
The labs are and should be targeted to a specific release for exactly
the reason you just discovered - in this case, the main metadata
promoted various QA Issues into errors immediately following the
release. In this case you were lucky and hit an example of something
obvious, most of the time it's not that obvious - basically if you do
anything outside of what's specified in the labs, especially working
from master, all bets are off...
Tom
> rday
>
next prev parent reply other threads:[~2013-04-09 0:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-08 15:41 working my way through the kernel hands-on labs finally Robert P. J. Day
2013-04-08 15:59 ` Bruce Ashfield
2013-04-08 16:02 ` Robert P. J. Day
2013-04-08 16:03 ` Bruce Ashfield
2013-04-08 16:07 ` Robert P. J. Day
2013-04-09 0:58 ` Tom Zanussi [this message]
2013-04-09 11:32 ` Robert P. J. Day
2013-04-09 21:10 ` Trevor Woerner
2013-04-09 21:29 ` Robert P. J. Day
2013-04-09 21:34 ` Trevor Woerner
2013-04-09 21:41 ` Robert P. J. Day
2013-04-09 21:46 ` Robert P. J. Day
2013-04-09 22:06 ` Trevor Woerner
2013-04-09 22:11 ` Tom Zanussi
2013-04-09 22:13 ` Robert P. J. Day
2013-04-09 22:17 ` Trevor Woerner
2013-04-26 1:30 ` Trevor Woerner
2013-05-01 20:51 ` Darren Hart
2013-04-09 22:29 ` Robert P. J. Day
2013-04-09 22:34 ` Trevor Woerner
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=1365469127.17697.70.camel@empanada \
--to=tom.zanussi@intel.com \
--cc=rpjday@crashcourse.ca \
--cc=yocto@yoctoproject.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.