All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Zanussi <tom.zanussi@intel.com>
To: Trevor Woerner <twoerner@gmail.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Updated Yocto Hands-on Kernel Lab available
Date: Mon, 18 Feb 2013 00:28:55 -0600	[thread overview]
Message-ID: <1361168935.27904.25.camel@empanada> (raw)
In-Reply-To: <CAHUNapRj7r+u500hA4WSc3TMMo85E9yJSrUinfcR7P+6WgU-tA@mail.gmail.com>

On Sun, 2013-02-17 at 21:16 -0500, Trevor Woerner wrote:
> ...sorry, I meant to CC the list too
> 
> 
> ---------- Forwarded message ----------
> From: Trevor Woerner <twoerner@gmail.com>
> Date: Sun, Feb 17, 2013 at 9:15 PM
> Subject: Re: [yocto] Updated Yocto Hands-on Kernel Lab available
> To: Tom Zanussi <tom.zanussi@intel.com>
> 
> 
> Hi Tom,
> 
> I can see how the kernel *.bb files get pulled in due to the following
> line in each lab's layer configuration (${LAYERDIR}/conf/layer.conf):
> 
>     BBFILES := "... ${LAYERDIR}/recipes-*/*/*.bb ..."
> 
> Since the *.bb files are located under
> ${LAYERDIR}/recipes-kernel/linux/<kernel>.bb this matched the above
> pattern.
> 
> What I can't figure out is why, for example, in lab1 are the kernel
> patch files located in
> 
>     ${LAYERDIR}/recipes-kernel/linux/linux
> 
> while the kernel patch files for lab2 are in
> 
>     ${LAYERDIR}/recipes-kernel/linux/files
> 
> Does bitbake find the patch files for lab1 in a subdirectory called
> "linux" because the recipe's name is linux_3.0.18.bb? Because I don't
> see anything in that particular recipe which would suggest it
> (bitbake) should look there (linux). And when I go to lab2 and rename
> the "files" directory to "linux-yocto" the build doesn't work, so this
> behaviour would seem to discount the belief that a patch directory
> name can take on the recipe name and be found.
> 

Hi,

Yes, in lab1 bitbake finds the patch files because they're in the
'linux' subdirectory.  It should also be able to find them if you
renamed that directory to 'linux-3.0.18', and it would also find them in
the 'files' directory.  These subdirectories are added to FILESPATH in
base.bbclass:

FILESPATH = "${@base_set_filespath(["${FILE_DIRNAME}/${BP}", "${FILE_DIRNAME}/${BPN}", "${FILE_DIRNAME}/files"], d)}"

Those are relative to a .bb, which is what we have in lab1 - the kernel
recipe is linux_3.0.18.bb.

In lab2, we have a linux-yocto_3.4.bbappend file rather than a .bb file.

If you look at the .bbappend, you can see:

FILESEXTRAPATHS_prepend := "${THISDIR}/files:"

which is what we need to add to the .bbappend to get bitbake to look in
the 'files' subdirectory under the .bbappend - since the FILESPATH is
relative to the base recipe in meta/, linux-yocto_3.4.bb, and not
our .bbappend, bitbake won't find the files under our .bbappend unless
we add our .bbappend's 'files' subdir to FILESPATH via FILESEXTRAPATHS. 

If you wanted to change the name of the directory under the .bbappend to
'linux-yocto', you could just use:

FILESEXTRAPATHS_prepend := "${THISDIR}/linux-yocto:"

or better:

FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"

Tom

> Best regards,
>     Trevor
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto




  reply	other threads:[~2013-02-18  6:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-16  2:29 Updated Yocto Hands-on Kernel Lab available Tom Zanussi
2013-02-16  2:54 ` Stewart, David C
     [not found] ` <CAHUNapRsL+R2+inZztqdTBfVM9EZNtgTWayjLWXE_6tQnd+6Mw@mail.gmail.com>
2013-02-18  2:16   ` Trevor Woerner
2013-02-18  6:28     ` Tom Zanussi [this message]
2013-02-18 23:50 ` Trevor Woerner
2013-02-19  5:31   ` Tom Zanussi
2013-02-19 10:31     ` Trevor Woerner
2013-02-19 17:45       ` Tom Zanussi
2013-02-20  3:34         ` Trevor Woerner
2013-02-20 18:48           ` Tom Zanussi

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=1361168935.27904.25.camel@empanada \
    --to=tom.zanussi@intel.com \
    --cc=twoerner@gmail.com \
    --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.