Re: [PATCH 1/1] meta-isar/isar-image-base: make kernel optional

[Claudius Heine <claudius.heine.ext@siemens.com>]

Hi Baurzhan,

On 2018-04-13 13:23, Baurzhan Ismagulov wrote:
> On Fri, Apr 13, 2018 at 12:45:10PM +0200, Claudius Heine wrote:
>>> If I want to generate an NFS rootfs w/o the kernel and an SD image
>>> with one,
>>> how would I proceed?
>>
>> With two multiconfigs? That would be how I would probably do it.
> 
> One multiconfig (e.g, qemui386-stretch), product-image-base.bb,
> product-nfs-base.bb.

You are right. Two multiconfigs would not be the best idea. Also since 
that would double the required resources. I haven't done this before, 
since I only create nfs root file systems for my project.

>>>   Do I understand correctly, the latter recipe would list
>>> this line, and the former would not?
>>
>> I don't understand your question here. What do you mean with 'latter'
>> and 'former recipe'?
> 
> Include IMAGE_INSTALL += "..." in product-image-base.bb but not in
> product-nfs-base.bb?

You could also just require the isar-image-base recipe on both images 
and set 'KERNEL_NAME' to "" in 'product-nfs-base.bb'. With this patch no 
kernel would be used.

AFAIK most people base their custom images on isar-image-base, so it 
makes sense to have this image parameterized. A general dependency like 
it was done before this patch is not that flexible.

Cheers,
Claudius

-- 
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-54 Fax: (+49)-8142-66989-80 Email: ch@denx.de