Yocto + meta-networking

Yocto + meta-networking

[Brian Hutchinson]

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

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:

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

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

Re: Yocto + meta-networking

[Saul Wold]

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@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>

Re: Yocto + meta-networking

[Paul Eggleton]

Hi Brian,

On Tuesday 16 July 2013 17:06:46 Brian Hutchinson wrote:
> 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:
> 
> 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).

Mixing branches is the issue here. meta-networking added a LAYERDEPENDS on 
"core" which the denzil poky/OE-Core doesn't provide. This is just an 
incidental error though, if it hadn't failed on this you'd have hit other 
problems.

meta-networking wasn't even around in the denzil days. If you need net-snmp 
from there on top of denzil the only way is to backport the recipe and any 
missing dependencies and add it to an additional layer (assuming you don't 
already have a layer for customisations). In practice backporting should be 
fairly trivial; I'd suggest copying the recipe over and seeing how far you 
get.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre

Re: Yocto + meta-networking

[Brian Hutchinson]

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

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@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@yoctoproject.org
>> https://lists.yoctoproject.**org/listinfo/yocto<https://lists.yoctoproject.org/listinfo/yocto>
>>
>>

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

Re: Yocto + meta-networking

[Brian Hutchinson]

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

On Tue, Jul 16, 2013 at 5:28 PM, Paul Eggleton <
paul.eggleton@linux.intel.com> wrote:

> Hi Brian,
>
> On Tuesday 16 July 2013 17:06:46 Brian Hutchinson wrote:
> > 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:
> >
> > 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).
>
> Mixing branches is the issue here. meta-networking added a LAYERDEPENDS on
> "core" which the denzil poky/OE-Core doesn't provide. This is just an
> incidental error though, if it hadn't failed on this you'd have hit other
> problems.
>
> meta-networking wasn't even around in the denzil days. If you need net-snmp
> from there on top of denzil the only way is to backport the recipe and any
> missing dependencies and add it to an additional layer (assuming you don't
> already have a layer for customisations). In practice backporting should be
> fairly trivial; I'd suggest copying the recipe over and seeing how far you
> get.
>
> Cheers,
> Paul
>
>
Thanks Paul, I worried about mixing branches since I've never tried that
before.  The only reason I picked Denzil is because I need ti816x support
and Dylan and Danny don't have machine confs for it in meta-ti.  So what
would be easier, getting the machine support I need in Dylan or back
porting the net-snmp recipe to Denzil?

Regards,

Brian

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

Re: Yocto + meta-networking

[Paul Eggleton]

On Wednesday 17 July 2013 08:56:34 Brian Hutchinson wrote:
> Thanks Paul, I worried about mixing branches since I've never tried that
> before.  The only reason I picked Denzil is because I need ti816x support
> and Dylan and Danny don't have machine confs for it in meta-ti.  So what
> would be easier, getting the machine support I need in Dylan or back
> porting the net-snmp recipe to Denzil?

I don't have a feel for the former - if the reason is not already clear you'd 
probably want to ask the meta-ti folks why that machine isn't supported in 
later branches and how hard it would be to update support. This might be worth 
doing if you're starting something new with denzil, since that's two versions 
behind current stable.

Having said that, backporting the net-snmp recipe should be fairly trivial 
though.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre

Re: Yocto + meta-networking

[Brian Hutchinson]

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

On Wed, Jul 17, 2013 at 9:03 AM, Paul Eggleton <
paul.eggleton@linux.intel.com> wrote:

> On Wednesday 17 July 2013 08:56:34 Brian Hutchinson wrote:
> > Thanks Paul, I worried about mixing branches since I've never tried that
> > before.  The only reason I picked Denzil is because I need ti816x support
> > and Dylan and Danny don't have machine confs for it in meta-ti.  So what
> > would be easier, getting the machine support I need in Dylan or back
> > porting the net-snmp recipe to Denzil?
>
> I don't have a feel for the former - if the reason is not already clear
> you'd
> probably want to ask the meta-ti folks why that machine isn't supported in
> later branches and how hard it would be to update support. This might be
> worth
> doing if you're starting something new with denzil, since that's two
> versions
> behind current stable.
>
> Having said that, backporting the net-snmp recipe should be fairly trivial
> though.
>
> Thanks.  Yea, with Classic everything was just there (warts and all) and
as I move more of our platforms to OE-Core I find that support for machines
(some old, some new) or recipes that I used to use aren't there so I'm not
too adept to figuring out how to wire everything back together to get what
I need.  I use the oe layer index search feature a lot! :)

Regards,

Brian

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

Re: Yocto + meta-networking

[Brian Hutchinson]

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

... thought I'd give an update.  I switched all branches to use master and
I was able to build packages from meta-networking (and others) just fine.

Thanks again for straightening me out!

Regards,

Brian

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

Re: Yocto + meta-networking

[Paul Eggleton]

On Tuesday 23 July 2013 10:36:46 Brian Hutchinson wrote:
> ... thought I'd give an update.  I switched all branches to use master and
> I was able to build packages from meta-networking (and others) just fine.
> 
> Thanks again for straightening me out!

Great!

One thing to keep in mind though, master is the development branch so it does 
occasionally break, so if you'd prefer something a bit more stable I'd suggest 
the most recent stable release tag or branch (currently dylan-9.0.1 or dylan 
respectively).

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre

Re: Yocto + meta-networking

[Brian Hutchinson]

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

On Tue, Jul 23, 2013 at 10:58 AM, Paul Eggleton <
paul.eggleton@linux.intel.com> wrote:

> On Tuesday 23 July 2013 10:36:46 Brian Hutchinson wrote:
> > ... thought I'd give an update.  I switched all branches to use master
> and
> > I was able to build packages from meta-networking (and others) just fine.
> >
> > Thanks again for straightening me out!
>
> Great!
>
> One thing to keep in mind though, master is the development branch so it
> does
> occasionally break, so if you'd prefer something a bit more stable I'd
> suggest
> the most recent stable release tag or branch (currently dylan-9.0.1 or
> dylan
> respectively).
>
>
I know its the bleeding edge but I need a specific version of a package and
at the moment it is only in master.  I guess I could back port it but I'm
hoping that before I need to do a release, there will be another yocto
release that will include the version I need in a released branch ;)

Regards,

Brian

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

Re: Yocto + meta-networking

[Denys Dmytriyenko]

On Wed, Jul 17, 2013 at 02:03:41PM +0100, Paul Eggleton wrote:
> On Wednesday 17 July 2013 08:56:34 Brian Hutchinson wrote:
> > Thanks Paul, I worried about mixing branches since I've never tried that
> > before.  The only reason I picked Denzil is because I need ti816x support
> > and Dylan and Danny don't have machine confs for it in meta-ti.  So what
> > would be easier, getting the machine support I need in Dylan or back
> > porting the net-snmp recipe to Denzil?
> 
> I don't have a feel for the former - if the reason is not already clear you'd 
> probably want to ask the meta-ti folks why that machine isn't supported in 
> later branches and how hard it would be to update support. This might be worth 

Just to update everyone on this list - the issue with ti81x has been discussed 
on meta-ti list multiple times before and Brian already knew the answer to that.


> doing if you're starting something new with denzil, since that's two versions 
> behind current stable.
> 
> Having said that, backporting the net-snmp recipe should be fairly trivial 
> though.

-- 
Denys