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

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

Hi Jan,

On 2018-04-16 09:09, Jan Kiszka wrote:
> On 2018-04-16 09:03, [ext] Claudius Heine wrote:
>> 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.
> 
> Why would it double the used resources? If two multiconfigs use the same
> machine and distro and only vary in the selected image, and that maybe
> only in a small package set (image B is based on image A), that should
> allow for massive sharing. Keep in mind that different multiconfig does
> not mean at all different basis (machine, distro, base image).

Sorry, I am currently not that into the path structure of Isar. I just 
use the variables, but haven't looked at their values in detail.
I thought, without checking, that the multiconfig name was part of some 
of those paths. Since multiconfigs select the kernels so they have to be 
part of the image name and maybe other paths as well to not cause 
conflict if multiple multiconfigs use the same machine and distro but 
different kernels.

Best regards,
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