[oe] Building a rootfs, without building a kernel

[Rodrigo Vivi]

I'm using
ASSUME_PROVIDED += "linux virtual/kernel"

It is enough when you don't want to build a package like iptables that has
RRECOMMENDS = "kernel-module-ip-tables kernel-module-iptable-filter"

But I believe that in this case you could add this recommends to
assume_provided.

On Thu, Jul 3, 2008 at 2:20 PM, Philip Balister <philip at balister.org> wrote:
> Welch, Martyn (GE EntSol, Intelligent Platforms) wrote:
>>
>> Ben Lau wrote:
>>>>
>>>> Possibly, we should create a dummy kernel bb file since this may be
>>>> the best solution for the general case of people building images
>>>> without a working kernel bb file.
>>>> Philip
>>>>
>>> I am not quite understand why OpenEmbedded force to generate kernel
>>> and the dependence would force it to be installed in the user land. As
>>> the kernel is usually installed on another partition. It should not be
>>> a part of the file system image.
>>>
>>
>> But any drivers, etc. built as modules would need to be included in the
>> system's image and that at least would be a dependence.
>
> Agreed. The image recipes have most modules included as RECOMMENDS so the
> image builds even if the module is not present. The technique I am using is
> for cases when you need a rootfs, before you have a working kernel recipe.
> You can copy the modules onto the rootfs if needed.
>
> Philip
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel at lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
>



-- 
Rodrigo Vivi
INdT - Instituto Nokia de Tecnologia
Blog: http://blog.vivi.eng.br
GPG: 0x905BE242 @ wwwkeys.pgp.net