Hi,

> -----Original Message-----
> From: Jan Kiszka [mailto:jan.kiszka@siemens.com]
> Sent: Tuesday, August 18, 2020 10:56 PM
> To: iwamatsu nobuhiro(岩松 信洋 □ＳＷＣ◯ＡＣＴ) <nobuhiro1.iwamatsu@toshiba.co.jp>; cip-dev@lists.cip-project.org
> Subject: Re: [cip-dev] [isar-cip-core][PATCH 1/3] cip-core-image-test: Add recipe
> 
> On 18.08.20 15:47, nobuhiro1.iwamatsu@toshiba.co.jp wrote:
> > Hi,
> >
> >> -----Original Message-----
> >> From: Jan Kiszka [mailto:jan.kiszka@siemens.com]
> >> Sent: Tuesday, August 18, 2020 2:30 PM
> >> To: cip-dev@lists.cip-project.org; iwamatsu nobuhiro(岩松 信洋 □ＳＷＣ◯ＡＣＴ)
> <nobuhiro1.iwamatsu@toshiba.co.jp>
> >> Subject: Re: [cip-dev] [isar-cip-core][PATCH 1/3] cip-core-image-test: Add recipe
> >>
> >> On 18.08.20 06:57, Nobuhiro Iwamatsu wrote:
> >>> Hi Jan,
> >>>
> >>> Could you comment on this patch series?
> >>>
> >>
> >> Ah, yeah, sorry.
> >>
> >> I think now it's better to model that as extension of an image, given
> >> that we already have two (regular + security). Or will we implicitly
> >> test the security image via the regular one?
> >>
> >
> > I see.
> > When extended, the resulting image will have the same filename as the base.
> > It's difficult to distinguish, so it's implemented as it is now.
> > If you know how to change the generated image file name by yaml file, please let me know.
> 
> Isar does not yet allow to override the image name. You'd basically have
> to weaken its setting like this
> 
> [isar/meta/classes/image.bbclass]
> IMAGE_FULLNAME ?= "${PN}-${DISTRO}-${MACHINE}"
> 
> and then you could override IMAGE_FULLNAME as desired.

I see. Thanks for your comment.
I will update function for allow to override IMAGE_FULLNAME, and I will resend the updated patch.

> 
> Jan
> 

Best regards,
  Nobuhiro

> --
> Siemens AG, Corporate Technology, CT RDA IOT SES-DE
> Corporate Competence Center Embedded Linux