[yocto] Yocto + meta-networking
Brian Hutchinson
b.hutchman at gmail.com
Tue Jul 16 14:47:39 PDT 2013
Hi Saul,
Sorry for top posting, I'm responding on my phone.
Yes, that's exactly how my bblayers.conf looks except when I had the first
problem I then added in meta-oe. I'll double check and make sure I didn't
do something stupid like use a spoiled shell env etc.
Note, I didn't check out meta-openembedded to layers dir, I did it in the
same dir as poky ... maybe that is my problem.
Regards,
Brian
On Jul 16, 2013 5:19 PM, "Saul Wold" <sgw at linux.intel.com> wrote:
> On 07/16/2013 02:06 PM, Brian Hutchinson wrote:
>
>> Hi,
>>
>> What is the "right" way of adding the meta-networking to Yocto? I'm
>> obviously not doing something right.
>>
>> At the poky directory level, I cloned meta-openembedded. I then tried
>> to go to my build's local.conf and adding meta-networking and meta-oe
>> layers and I'm getting a dependency message when I try to bitbake
>> net-snmp that says:
>>
>> Did you mean your bblayers.conf file? I am not sure you need meta-oe if
> you are just building net-snmp, this is what your bblayers.conf should look
> like:
>
> BBLAYERS ?= " \
> /home/sgw/yocto/poky/meta \
> /home/sgw/yocto/poky/meta-**yocto \
> /home/sgw/yocto/poky/meta-**yocto-bsp \
> /home/sgw/yocto/layers/meta-**openembedded/meta-networking \
> "
>
> This is from a POKY build, if this is oe-core alone then you would not
> have the meta-yocto* layers.
>
> Sau!
>
>
> ERROR: Layer dependency core of layer networking not found
>>
>> This makes me think that meta-openembedded is wanting openembedded-core
>> but I've never tried to use that with Yocto before so I thought I better
>> ask before I totally mess up my build environment.
>>
>> I have a rootfilesystem build based on Denzil and I need net-snmp and
>> the meta-networking Denzil branch is pretty much empty so I cloned
>> master in order to get net-snmp so I don't know if mixing branches could
>> be my problem (don't know how much that matters but I usually try to use
>> the same release branch of various components).
>>
>> I've looked for examples of this kind of setup but haven't found much.
>>
>> Regards,
>>
>> Brian
>>
>>
>>
>> ______________________________**_________________
>> yocto mailing list
>> yocto at yoctoproject.org
>> https://lists.yoctoproject.**org/listinfo/yocto<https://lists.yoctoproject.org/listinfo/yocto>
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20130716/ae3a2fa1/attachment.html>
More information about the yocto
mailing list