[oe] generate a named kernel in ${DEPLOY_DIR_IMAGE}

[Denys Dmytriyenko]

On Wed, Sep 29, 2010 at 08:28:37AM +0200, Frans Meulenbroeks wrote:
> 2010/9/29 Andrea Adami <andrea.adami at gmail.com>:
> > On Tue, Sep 28, 2010 at 6:54 PM, Frans Meulenbroeks
> >> As I needed to generate two different kernels for the same machine I
> >> had some kind of problem (as emailed yesterday).
> >> For now I've solved it as follows:
> >>
> >> I created a 2nd recipe (in an overlay):
> >> linux-small_2.6.34.bb
> >> this one essentially only requires linux_2.6.34.bb and sets S to the linux_${PN}
> >> Then I can just add a dir linux-small and add the small defconfig in it.
> >>
> >> That way bitbake linux-small should give me the 2nd kernel.
> >> And actually it builds the kernel but this one is also packaged in a
> >> kernel-*.ipk.
> >> I could have made two different machines, but that seemed somewhat
> >> overkill, so in the end I decided to modify do_install_append in
> >> linux.inc.
> 
> PS: referring to Denys' message about multi-linux.inc: still haven't
> tested it, but what isslightly nasty about it is that it does not
> package, so I cannot easily include modules in an image
> (as my kernels are from the same recipe the modules are compatible,
> and it helps to be able to say in an image recipe that you want to add
> kernel-module-xyz)

Frans,

It packages only the main kernel and all the related modules, configured by 
the usual defconfig file. But it doesn't do it for the additional kernels that 
were built using configuration files from configs/ directory...

-- 
Denys