> >>>>>>> Think I've followed the example in the manual correctly. My
> >>>>>>> append file
> >>>> is
> >>>>>> pretty simple:
> >>>>>>>
> >>>>>>> FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}"
> >>>>>>
> >>>>>> It looks like you forgot the colon at the end of the path.
> >>>>>> Try this:
> >>>>>> FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
> >>>>>>
> >>>>>> -Kevin
> >>>>>
> >>>>> Good eye, but afraid that didn't help (maybe the path was empty
> >>>> before???). I think the files are getting picked up, since fetch
> >>>> will fail if change the file name to force a not found error.
> >>>>>
> >>>>
> >>>> What release are you using ? I tested this just last night before
> >>>> the
> >>>> 1.4 release final RC .. so it definitely still works!
> >>>>
> >>>> How are you determining that it isn't being picked up?
> >>>
> >>> I believe the SDK is based on Yocto 1.2 / Poky 7.0 -- bitbake is 1.15.2.
> >>> kernel.bbclass kernel_do_configure() looks like it only does a make
> >> oldconfig on defconfig...?
> >>> Should I expect to see the .cfg files being eppended there?
> >>>
> >>> The .config I end up with doesn't have the definitions from my .cfg
> >> fragment files.
> >>
> >> Fragments are processed later in the build procedure. Assuming this
> >> is a linux-yocto based bbappend, they'll be added in the
> >> kernel_configme task, and will modify the base BSP configuration.
> >>
> >> That doesn't mean that all the settings will make it to the final
> >> .config, since normal LKC processing and missing dependencies would
> >> drop invalid/incorrect settings.
> >
> > The SDK .bb inherits directly from kernel & doesn't use linux-yocto.bb. So
> listtask doesn't show configme.
> > I see an addtask for it in linux-yocto.inc, but am guessing that trying to
> shoehorn that in on top of the SDK (in my append file) is probably more
> trouble than it's worth.
> > Guess I'm better off trying to figure out how to patch the defconfig?
>
> The ability to use fragments requires that you at least use the linux-yocto
> bbclass, it will work with non linux-yocto recipes, but you need to follow the
> example in meta-skeleton/recipes-kernel/linux/linux-yocto-custom.bb
>
> The 1.2 vintage fragments aren't as feature rich as 1.3 and 1.4, but they
> should work to add simple fragment modifications.
>
> I hate to see anyone hacking a defconfig unless nothing else works :)
Thanks for all the help. The skeleton example isn't in 1.2. Based on 1.3 I
tried adding
require recipes-kernel/linux/linux-yocto.inc
to my append, but ran into other errors (looks like it adds 5 tasks including
kernel_configme). Did a brute-force override of do_kernel_checkout() to get
around my 1st error, but then do_patch() failed, so think I'm going to punt &
hack defconfig.
Thanks again for all the help.
>
> Bruce
>
> >
> >
> >>
> >> Cheers,
> >>
> >> Bruce
> >>
> >>>
> >>>>
> >>>> Cheers,
> >>>>
> >>>> Bruce
> >
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
