From: Jack Mitchell <ml@communistcode.co.uk>
To: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Is there a recipe for evtest package?
Date: Mon, 30 Jan 2012 09:32:38 +0000 [thread overview]
Message-ID: <4F2663B6.1030801@communistcode.co.uk> (raw)
In-Reply-To: <CAEsOVNfPSCTTyVDmmOfqF52FXoWajDZtY-n9MNq0mVn+kUw_wg@mail.gmail.com>
On 28/01/12 02:16, McClintock Matthew-B29882 wrote:
> On Wed, Jan 25, 2012 at 7:36 AM, Brian Hutchinson<b.hutchman@gmail.com> wrote:
>> On Wed, Jan 25, 2012 at 9:48 AM, Jack Mitchell<ml@communistcode.co.uk> wrote:
>>> Hi Brian,
>>>
>>> Your best bet is to adapt the one from meta-oe here:
>>>
>>> http://cgit.openembedded.org/meta-openembedded/tree/meta-oe/recipes-support/evtest
>> Hi Jack,
>>
>> I'm still trying to get up-to-speed on how to work with Yocto ....
>> would adding this layer be just like adding say poky extras?
> Yes, although other issues can present itself. If you start using
> meta-oe you need to make sure you pick one that is compatible with
> your oe-core layer.
>
> -M
Just to wrap this up, I was suggesting he take a single recipe from
meta-oe, bring it into his own layer and adapt it to fit the Yocto build
environment.
I would be interested to know, how Yocto and OE are working together. Is
the aim of the game to merge features upstream to OE and then on the
back of that packages in meta-oe will be easier to transfer into a Yocto
layer? I try to keep on top of the OE mailing lists but as I'm sure you
know they're much higher volume than this list and are often solely
patch based rather than discussion.
Cheers,
Jack.
prev parent reply other threads:[~2012-01-30 9:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-25 14:42 Is there a recipe for evtest package? Brian Hutchinson
2012-01-25 14:48 ` Jack Mitchell
2012-01-25 15:36 ` Brian Hutchinson
[not found] ` <4F20239F.2010407@communistcode.co.uk>
2012-01-25 15:59 ` Brian Hutchinson
2012-01-28 2:16 ` McClintock Matthew-B29882
2012-01-30 9:32 ` Jack Mitchell [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=4F2663B6.1030801@communistcode.co.uk \
--to=ml@communistcode.co.uk \
--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.