Re: [PATCH 1/1] classes/image: Separate image rootfs for machines

[Jan Kiszka <jan.kiszka@siemens.com>]

On 11.03.19 18:03, Maxim Yu. Osipov wrote:
> Signed-off-by: Maxim Yu. Osipov <mosipov@ilbers.de>
> ---
>   meta/classes/image.bbclass | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/meta/classes/image.bbclass b/meta/classes/image.bbclass
> index 2514c88..ed9d6eb 100644
> --- a/meta/classes/image.bbclass
> +++ b/meta/classes/image.bbclass
> @@ -3,7 +3,7 @@
>   
>   IMAGE_INSTALL ?= ""
>   IMAGE_TYPE    ?= "ext4-img"
> -IMAGE_ROOTFS   = "${WORKDIR}/rootfs"
> +IMAGE_ROOTFS   = "${WORKDIR}/${MACHINE}/rootfs/"
>   
>   IMAGE_INSTALL += "${@ ("linux-image-" + d.getVar("KERNEL_NAME", True)) if d.getVar("KERNEL_NAME", True) else ""}"
>   
> 

Hmm, I wonder if that is actually a sufficient change - or a needed one. Just 
checked jailhouse-images, and there I do

PN .= "-${MACHINE}"

in the image recipe to ensure that distinct images (in different IMAGE_ROOTFS) 
are built. That change above will still run the recipe multiple times, 
overwriting at least the logs in confusing ways, if not more, no?

Jan

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