[poky] How do I apply a patch to a wic configuration file (beagle bone-yocto.wks)?
Khem Raj
raj.khem at gmail.com
Fri Jun 15 21:30:42 PDT 2018
On Fri, Jun 15, 2018 at 3:47 PM Marc Pernia
<marc.pernia at redaptiveinc.com> wrote:
>
> Hey Khem, thanks for your prompt response!
>
> How would I go about defining my own kickstart file? Our board was designed based on the BBG reference design, so we use the beaglebone-yocto bsp layer, alas, we don’t manage a machine configuration in our layer.
> Is there another way to define WKS_FILE from our layer? ...in place of the WKS_FILE defined in the bsp layer that isn’t owned by us?
The machine config metadata defines it as a weak assignment see
WKS_FILE ?= "beaglebone-yocto.wks"
so you should be able to override it in config metadata in your own
layer to point to a different
file ( may be even in local.conf file )
WKS_FILE = "your-beaglebone-yocto.wks"
you might be able to use machine override as well
WKS_FILE_beaglebone-yocto = "your-beaglebone-yocto.wks"
then you can put the new wks file in
meta-<your-layer>/wic/
>
> SLR-
>
> On 6/15/18, 2:34 PM, "Khem Raj" <raj.khem at gmail.com> wrote:
>
> Hi Marc
>
> On 6/14/18 11:51 PM, Marc Pernia wrote:
> > I need to patch meta-yacto-bsp/wic/beaglebone-yocto.wks. I have a patch
> > ready, but how can I apply that patch from a recipe in my custom layer.
> > All the patching I have done in the past has been done with a bbappend
> > created for an existing bb file; this time the target has no bb file,
> > its a .wks file.
> >
>
> You can define a new wks file in your layer since the default you are
> referring to above is a reference. And if your changes are good for this
> reference then please post these modifications to yocto mailing list.
>
> Otherwise, if the wks file is specific to image format you want for your
> devices then keeping that to your layer would be right thing to do.
>
> >
> >
> > SLR-
> >
> >
>
>
>
>
More information about the poky
mailing list