All of lore.kernel.org
 help / color / mirror / Atom feed
From: "David Nyström" <david.nystrom@enea.com>
To: <yocto@yoctoproject.org>
Subject: Re: Recipe question - source directory of depency parent
Date: Thu, 7 Jun 2012 21:45:23 +0200	[thread overview]
Message-ID: <4FD104D3.6040007@enea.com> (raw)
In-Reply-To: <4FD0FE67.6090801@enea.com>

Oops,

That should be ${STAGING_KERNEL_DIR}

Br,
David

On 06/07/2012 09:17 PM, David Nyström wrote:
> Have a look at: 
> poky/meta-skeleton/recipes-kernel/hello-mod/hello-mod_0.1.bb
> Use ${KERNEL_STAGING_DIR} to locate kernel sources.
>
> Br,
> David
>
> On 06/07/2012 09:12 PM, Jim Rucker wrote:
>> I'm creating a bitbake recipe for a package that is a loadable 
>> module, but
>> it requires the linux source directory in order to build. I added the
>> virtual/kernel package as our "DEPENDS", but when I run bitbake -e 
>> for my
>> target I don't see an environment variable that specifies where the 
>> source
>> is for the virtual/kernel package. Is there a way to get this, or am 
>> doing
>> this wrong? I put the .bb recipe in the same
>> meta-ourco/recipes-kernel/linux directory that has the .bb which 
>> builds the
>> linux kernel for our target, but in its own file, with its own 
>> "PROVIDES"
>> variable.
>>
>>
>>
>> _______________________________________________
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto



      reply	other threads:[~2012-06-07 19:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-07 19:12 Recipe question - source directory of depency parent Jim Rucker
2012-06-07 19:17 ` David Nyström
2012-06-07 19:45   ` David Nyström [this message]

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=4FD104D3.6040007@enea.com \
    --to=david.nystrom@enea.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.