From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6667603680306397184 X-Received: by 2002:a2e:81ce:: with SMTP id s14mr450791ljg.3.1552548503418; Thu, 14 Mar 2019 00:28:23 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a2e:9e18:: with SMTP id e24ls593083ljk.9.gmail; Thu, 14 Mar 2019 00:28:22 -0700 (PDT) X-Google-Smtp-Source: APXvYqwcTGTKuNTy89WfZ98QxELF4d6EupnpZIfoAhac5eiPPQDfbLU1EQPMGxTeYE2etiIgLf7N X-Received: by 2002:a2e:80c7:: with SMTP id r7mr2859349ljg.10.1552548502907; Thu, 14 Mar 2019 00:28:22 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1552548502; cv=none; d=google.com; s=arc-20160816; b=u/wIwaVz+PJtIWsjNG4voM+R0AoZlvYIANw8Nb3vmsKkipYN2yXP9OeON/HJTxA4VG osivgA14WNzWMVPpD9cMC6Ya7Avnx4knTJKecUiZ4uw+IOJI4pNHpStBe8w+6COgU2EJ 9rPyBtDvPoXiZhZo233x4dcHm21PXerOX6qlBLx98PnooKZyWSwIzryfhVSaX6G4xLYa ylb0YmIV/dBkXMJPTTXVBfIVzDYosE28XDJYSKUWdrVNozmn5Qc5oDaJcElReCfx1+Ld ALRc3n4JQETHE7UUOn1MbvDIWAn+llwQYPmbL/jMpIW6NCfSD6Tq31yVs84Hb+iH+kUc gmXQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:content-language:in-reply-to:mime-version :user-agent:date:message-id:from:references:to:subject; bh=Ch8nM9q8d+IA8N42BdacXHcw9fsqQj9fM8L/E9YNwnw=; b=hS5TsGvm30DYn+/l5QdijhXRhpj7nSfksAdw52lux6FMWHUY2Cfx1Z16ESdF53EUQs 1ZJBNDn8hashWRvxEWVdoiA+fgqzQ5mmOliAZ0qMifngapkrZVwtqycgxatmFMfTJS/q D2V4Vg79zh2k2QwMBL2nMMOy7q2Rrxwyd8fywFuk/wseqOngIbLuoKvds9cyQ5Ge5FTN 6cRr9R0MKg1zpFBQsTTfEBV5qRIeY/0Xtp2sku9vomKJaJYn98jJ9rW55bZBHIfCikwQ U/6Ovb1SaZO2zLQd41T4Xqs6wRxQaBbQb70Agz9ckC76uFLbSHsA3QqU+DwU/Hy23/z1 51BQ== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of jan.kiszka@siemens.com designates 192.35.17.28 as permitted sender) smtp.mailfrom=jan.kiszka@siemens.com Return-Path: Received: from goliath.siemens.de (goliath.siemens.de. [192.35.17.28]) by gmr-mx.google.com with ESMTPS id f20si495513lfc.5.2019.03.14.00.28.22 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 14 Mar 2019 00:28:22 -0700 (PDT) Received-SPF: pass (google.com: domain of jan.kiszka@siemens.com designates 192.35.17.28 as permitted sender) client-ip=192.35.17.28; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of jan.kiszka@siemens.com designates 192.35.17.28 as permitted sender) smtp.mailfrom=jan.kiszka@siemens.com Received: from mail1.sbs.de (mail1.sbs.de [192.129.41.35]) by goliath.siemens.de (8.15.2/8.15.2) with ESMTPS id x2E7SLVc011320 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Thu, 14 Mar 2019 08:28:22 +0100 Received: from [167.87.11.54] ([167.87.11.54]) by mail1.sbs.de (8.15.2/8.15.2) with ESMTP id x2E7SKEU007389; Thu, 14 Mar 2019 08:28:21 +0100 Subject: Re: [PATCH 1/2] meta-isar: Separate images per MACHINE To: "[ext] Claudius Heine" , "Maxim Yu. Osipov" , isar-users@googlegroups.com References: <20190312202713.18792-1-mosipov@ilbers.de> <7984d051-8bf0-dff1-804d-104ad2a17af7@siemens.com> From: Jan Kiszka Message-ID: <6077c8f9-e72c-e51a-cbb2-d03645034c77@siemens.com> Date: Thu, 14 Mar 2019 08:28:20 +0100 User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); de; rv:1.8.1.12) Gecko/20080226 SUSE/2.0.0.12-1.1 Thunderbird/2.0.0.12 Mnenhy/0.7.5.666 MIME-Version: 1.0 In-Reply-To: <7984d051-8bf0-dff1-804d-104ad2a17af7@siemens.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-TUID: BkiTBgBPfjPq On 14.03.19 08:21, [ext] Claudius Heine wrote: > Hi Maxim, > > On 13/03/2019 17.42, Maxim Yu. Osipov wrote: >> Hi everybody, >> >> Any feedback on this patch? >> This is a "fast track" patch as it fixes problem which delayed the release. >> >> Thanks, >> Maxim. >> >> On 3/12/19 9:27 PM, Maxim Yu. Osipov wrote: >>> Image directory gets overwritten when running for two targets >>> with the same pair DISTRO and DISTRO_ARCH, resulting >>> start_vm script failure. >>> >>> Note: >>> This patch affects the bitbake multiconfig target calling syntax: >>> PREVIOUS: "multiconfig:$MACHINE-$DISTRO:isar-image-base" >>> NEW: "multiconfig:$MACHINE-$DISTRO:isar-image-base-$MACHINE" >>> >>> Suggested-by: Jan Kiszka >>> Signed-off-by: Maxim Yu. Osipov >>> --- >>>   meta-isar/conf/conf-notes.txt                    |  6 ++-- >>>   meta-isar/recipes-core/images/isar-image-base.bb |  2 ++ >>>   meta-isar/recipes-core/images/isar-image-ubi.bb  |  2 ++ >>>   scripts/ci_build.sh                              | 40 ++++++++++++------------ >>>   scripts/start_vm                                 | 16 +++++----- >>>   5 files changed, 35 insertions(+), 31 deletions(-) >>> >>> diff --git a/meta-isar/conf/conf-notes.txt b/meta-isar/conf/conf-notes.txt >>> index 87bd2dc..84049e1 100644 >>> --- a/meta-isar/conf/conf-notes.txt >>> +++ b/meta-isar/conf/conf-notes.txt >>> @@ -1,4 +1,4 @@ >>>   Common targets are: >>> -    multiconfig:qemuarm-stretch:isar-image-base >>> -    multiconfig:qemuamd64-stretch:isar-image-base >>> -    multiconfig:rpi-jessie:isar-image-base >>> +    multiconfig:qemuarm-stretch:isar-image-base-qemuarm >>> +    multiconfig:qemuamd64-stretch:isar-image-base-qemuamd64 >>> +    multiconfig:rpi-jessie:isar-image-base-rpi > > I am not a big fan of having to specify the machine when building a image. > > Would it be possible to have virtual recipes? > > IMO all isar-image-base-* would provide a isar-image-base. That would be useful if it has no unexpected side effects. Can we exclude that we end up with multiple providers in some scenario? It seems so, but I'm not 100% sure ATM. Jan -- Siemens AG, Corporate Technology, CT RDA IOT SES-DE Corporate Competence Center Embedded Linux