All of lore.kernel.org
 help / color / mirror / Atom feed
From: varun bhatnagar <varun292006@gmail.com>
To: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Yocto Layers not getting recognized by bitbake
Date: Mon, 17 Jun 2013 23:33:59 +0530	[thread overview]
Message-ID: <CAGxOggHuW93fygtGt037LLX1PFzgGzqDr3au1GV76hAaSnka6w@mail.gmail.com> (raw)
In-Reply-To: <51BF484F.9070009@mlbassoc.com>

[-- Attachment #1: Type: text/plain, Size: 1731 bytes --]

Actually the package which I am building is having some dependencies on
some libraries. So I provided those libraries with the help of creating
layers. I did not extract those from meta-openembedded, instead, I manually
created two layers and added them in bblayer.conf file. Now, after
configuring all this stuff I am again trying to recompile my code but still
I am getting the same error saying that it is not able to find those
libraries provided by me in the form of layers.


On Mon, Jun 17, 2013 at 11:03 PM, Gary Thomas <gary@mlbassoc.com> wrote:

> On 2013-06-17 18:08, varun bhatnagar wrote:
>
>> Hi,
>>
>> I am trying to compile my code using yocto. For that I have created two
>> layers: "meta-networking" and "meta-oe". I have added these dependencies in
>> bblayer.conf too. But these are
>> not getting build. Can anyone please tell me what should I do to make
>> this work.
>>
>
> More details are needed to be able to help.
>
> What do you mean "not getting built"?  Do you mean that if you
> try to build recipe XYZ which is in one of those layers that it's
> not being built?  Or perhaps you mean something else?
>
> What do you mean "created two layers: ..."?  Did you just extract
> these from meta-openembedded?  or something else?
>
> --
> ------------------------------**------------------------------
> Gary Thomas                 |  Consulting for the
> MLB Associates              |    Embedded world
> ------------------------------**------------------------------
> ______________________________**_________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.**org/listinfo/yocto<https://lists.yoctoproject.org/listinfo/yocto>
>

[-- Attachment #2: Type: text/html, Size: 2424 bytes --]

  reply	other threads:[~2013-06-17 18:03 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-17 17:08 Yocto Layers not getting recognized by bitbake varun bhatnagar
2013-06-17 17:33 ` Gary Thomas
2013-06-17 18:03   ` varun bhatnagar [this message]
2013-06-17 21:02     ` Sudhangathan B S
2013-06-18 16:28       ` varun bhatnagar
2013-06-18 16:41         ` Gary Thomas
2013-06-19 16:10           ` varun bhatnagar
2013-06-22 19:04             ` varun bhatnagar
2013-06-25 10:46               ` Paul Eggleton
2013-06-25 19:04                 ` varun bhatnagar
2013-06-25 19:13                   ` Saul Wold
2013-06-27 17:58                     ` varun bhatnagar
2013-06-27 20:25                       ` Paul Eggleton
2013-06-29 18:35                         ` varun bhatnagar
2013-07-01  9:48                           ` Paul Eggleton
2013-07-12 18:23                             ` varun bhatnagar

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=CAGxOggHuW93fygtGt037LLX1PFzgGzqDr3au1GV76hAaSnka6w@mail.gmail.com \
    --to=varun292006@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.