[poky] Simple recipe for local kernel/git development

[Bruce Ashfield]

On Wed, Feb 1, 2012 at 10:30 AM, Bruce Ashfield
<bruce.ashfield at gmail.com> wrote:
> On Wed, Feb 1, 2012 at 10:22 AM, O'donoghue, Bryan
> <bryan.odonoghue at intel.com> wrote:
>>> Are you working from yocto master ?
>>
>> Yes.
>>
>> Our "poky" directory is from a fairly recent yocoto pull ~ 3 weeks
>>
>>> That being said, if you aren't using meta or aren't using existing BSP
>>> patches (and
>>> branches), then starting from a yocto kernel tree isn't strictly
>>> required. In fact, it
>>> probably confuses things.
>>
>> It confuses me !
>
> It's simple enough, fragments are really handy, as are getting the feature
> patches and isolation board changes.
>
> But if this isn't something maintained, or that is something more of a transient
> thing, then doing any extra setup can be a pain.
>
>>
>>>
>>> The tools can work with a korg tree, using a defconfig, etc. In a nice
>>> coincidence, I'm
>>> completing re-validation of the example korg recipe today.
>>
>> Yes - assume this is a korg snapshot (it basically is)
>>
>> All I need to do is to build the korg snapshot from a local git repo and apply a defconfig (it sounds simple when you type it like that)
>
> Easily supported. I'll follow up once my fetches have completed here
> and I see that the
> recipe builds properly.

Sorry for the slow reply, I got bogged down fixing a few things.

I confirmed that the sample recipe I mentioned still builds. Although
I do have some
tweaks to things that I'm preparing for master at the moment. But they are
cosmetic/streamlining changes, not fundamental issues.

The recipe I was referring to is here:

  http://git.yoctoproject.org/cgit/cgit.cgi/poky-extras/tree/meta-kernel-dev/recipes-kernel/linux/linux-korg.bb

cloning poky-extras and looking in meta-kernel-dev will get you your own copy.

The recipe is intended to build kernel.org, or really any git
repository, plus a defconfig.

It creates some minimal infrastructure to work with the yocto tools,
and to create someplace
that work could be done, and then flipped into a formatted kernel
feature. But the branch that
is built is created automatically and directly off the point you
specify. Which in our case would
be master HEAD.

You'd need to tweak the kernel version, etc, but in the end it the
build system that consumes
and uses that, more than the kernel build itself.

Cheers,

Bruce



>
> Cheers,
>
> Bruce
>
>> -------------------------------------------------------------
>> Intel Ireland Limited (Branch)
>> Collinstown Industrial Park, Leixlip, County Kildare, Ireland
>> Registered Number: E902934
>>
>> This e-mail and any attachments may contain confidential material for
>> the sole use of the intended recipient(s). Any review or distribution
>> by others is strictly prohibited. If you are not the intended
>> recipient, please contact the sender and delete all copies.
>>
>
>
>
> --
> "Thou shalt not follow the NULL pointer, for chaos and madness await
> thee at its end"



-- 
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"