From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6708705003020746752 X-Received: by 2002:adf:f84f:: with SMTP id d15mr23044671wrq.53.1562062911776; Tue, 02 Jul 2019 03:21:51 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a1c:96cf:: with SMTP id y198ls694025wmd.5.canary-gmail; Tue, 02 Jul 2019 03:21:51 -0700 (PDT) X-Google-Smtp-Source: APXvYqx65UWDqwsnwvRLaLZflg4T7t2ZtoxJkoWJW623/plT0eFfszmXWt89nKtQLo7yvOaDXHuV X-Received: by 2002:a1c:407:: with SMTP id 7mr3130057wme.113.1562062911365; Tue, 02 Jul 2019 03:21:51 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1562062911; cv=none; d=google.com; s=arc-20160816; b=vrBtrs3I9EBsqHUkSuyCZkXfpK+wQUV7K6vAE0QbRvK2WCU7WDCdwrIf8OKX0pq8QM b1dIGcngFt/GnhuPgtHJ0Ws89MfMMlEcTtOZJI7nh9GVYxjfsNa4i36JnozaaicNEzix voSiXhpYOu28o9i+9C29oTECyEvBoHcR2fxmG0ennkxXjn5Q/g4JG7ZHOMXgKCwT+d/d /FMJVnORJUhOQAzPWaepaE6ycEpebAN40Kp+feCEM4GOVu/dNnDk+F+3jdJT6bmJji3N 3+g9W6sJAhLWVl1KdBiDaKnxnutASLJrPKqxsFETm007EDEcIrBTH88jXQK+KwBYDHY+ d8og== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date; bh=+64HHy2PftNtGsqWFY00zL7oyzzae0EE8j2PtoYv9Xw=; b=xBHcbYe+/c+x0S1cPlU+a4K7T3Y24tOKhHg9Qn0D+vcMYaypuuGmVEZvlQSOnR59UA hqqwviC3qIQv6MCcdfSXS1b6ByNkBG0Y7nq0CuvpG57wv8HuVRHO6BqiT1RgANSKkBlp xM5gmiXHGFyoxMQXk1oiWKyuh1GnyQg+QGQDo1vhr8U27b1AyiD0z4DDEvD0BJtpEDfZ BpSaQ88o8pAIYdhwniXKG0+pUXJ75OTzlqnnfBo41kRZ7lkMtFea2BdWvTNQVAy+qlzT VtIwJJ3Ajq4X4+XPsjQpErFM2VqIdh+JS11QPa89pvbwUV+iGMvUiLm29J9ntDU/wPFH +uDw== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of henning.schild@siemens.com designates 194.138.37.39 as permitted sender) smtp.mailfrom=henning.schild@siemens.com; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=siemens.com Return-Path: Received: from lizzard.sbs.de (lizzard.sbs.de. [194.138.37.39]) by gmr-mx.google.com with ESMTPS id t25si132110wmj.2.2019.07.02.03.21.51 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 02 Jul 2019 03:21:51 -0700 (PDT) Received-SPF: pass (google.com: domain of henning.schild@siemens.com designates 194.138.37.39 as permitted sender) client-ip=194.138.37.39; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of henning.schild@siemens.com designates 194.138.37.39 as permitted sender) smtp.mailfrom=henning.schild@siemens.com; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=siemens.com Received: from mail2.sbs.de (mail2.sbs.de [192.129.41.66]) by lizzard.sbs.de (8.15.2/8.15.2) with ESMTPS id x62ALoBN004145 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Tue, 2 Jul 2019 12:21:50 +0200 Received: from md1za8fc.ad001.siemens.net ([139.25.69.32]) by mail2.sbs.de (8.15.2/8.15.2) with ESMTP id x62ALojk003181; Tue, 2 Jul 2019 12:21:50 +0200 Date: Tue, 2 Jul 2019 12:21:49 +0200 From: Henning Schild To: "'Benedikt Niedermayr' via isar-users" Cc: Benedikt Niedermayr Subject: Re: multi MACHINE build for same DISTRO_ARCH Message-ID: <20190702122149.067d533b@md1za8fc.ad001.siemens.net> In-Reply-To: <091c680c-8836-0efd-acbb-68d306ae5305@googlemail.com> References: <091c680c-8836-0efd-acbb-68d306ae5305@googlemail.com> X-Mailer: Claws Mail 3.17.3 (GTK+ 2.24.32; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-TUID: EDjzz25tNBfH Hi, the key is to get the split between machine and distro configs right. And to make sure all your recipes create generic enough packages that can be shared or differ in name/version where not. The great sharing potential, reducing build time and size, but also means a high risk of false sharing if you make a mistake. I personally avoid multiconfig builds for that reason. Henning Am Mon, 1 Jul 2019 16:41:36 +0200 schrieb 'Benedikt Niedermayr' via isar-users : > Hi guys, >=20 > before I send some patches to you I would like to discuss this a bit. >=20 > The problem is to run multi machine builds for the same DISTRO_ARCH. >=20 > We have for example a BSP layer which supports imx6, imx7 and imx8=20 > architectures, and we like to be able to run >=20 > those builds within a single bitbake command: >=20 >=20 > bitbake multiconfig:imx6-stretch:isar-image-base \ >=20 > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0 multiconfig:imx7-stretch= :isar-image-base \ >=20 > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0 multiconfig:imx8-stretch= :isar-image-base >=20 >=20 > The build runs fine if DISTRO_ARCH differs between targets. But it > does not run successfully if only MACHINE differs and DISTRO_ARCH is > the same. >=20 >=20 > I think running multi machine build within one bitbake build folder=20 > makes a lot of sense, especially when it comes to build time and CI. >=20 > I don't like it to create a new build folder for every MACHINE, > although everything (rootfs, buildchroot, etc.) stays almost the same > among DISTRO_ARCHs. >=20 >=20 >=20 > Is anybody familiar with this behavior? >=20 >=20 >=20 > Thanks, >=20 > Benni >=20 >=20 >=20 >=20