From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6935390513328553984 X-Received: by 2002:a2e:b806:: with SMTP id u6mr14422845ljo.99.1614773396962; Wed, 03 Mar 2021 04:09:56 -0800 (PST) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a05:6512:3993:: with SMTP id j19ls969054lfu.3.gmail; Wed, 03 Mar 2021 04:09:55 -0800 (PST) X-Google-Smtp-Source: ABdhPJyWHxdiwT7MSLw1thd9E18QNS8Dx50GekUM9IDC1R3JICXMsVK0YcsvsQ10BeTjJqrYWxs/ X-Received: by 2002:a19:30c:: with SMTP id 12mr15792088lfd.102.1614773395854; Wed, 03 Mar 2021 04:09:55 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1614773395; cv=none; d=google.com; s=arc-20160816; b=OF/6psO9u9N1KvL8P5taBzB9BzUNQQpbM0l5pjbaS3XIi+0hPhsAUmPD9TYxtGRKMa QgInSaoOukkBm/CMFW2SVy94b8Q8Yag31Oull7dhRKHktwA2H8GHSp51IN2jCyj3Ljz9 tROXxBjbdU8yBjOuVPAs4+1T4jzqdMI2bt80yUbpI4QANyGtu2OYo47I2blMDG7YVT0I pSbslEm1CtdJkkt+VOigNYuCGMAUTZ3K1pK2t27Sf00YOsZPWFJX2R0ex1sl9kSvYu88 Ms7Ty630uDIPaAdcIPJWVfiMghrkSR7ftZhV8clXRaaeY1yf19mhqlDAUvrywNLr8A+V WYzQ== 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=7rPlg3UJPv9z7JjLNpLaj2llAAeVwij+Mfr1Z01FJ4M=; b=VJm9m2TAfNcDPYxFoo8ZpXZDZEIgaIRErt7OWHD5CDwc7dDJIigXnaIZWXsBFq7u8T /Mq4TB+a8npo/hsrWcSXM0g3XJYKvIlJhjQNLgzNkTiWqIAQWWgvcRnFLmY2/JSX0ENk a3ogxCc5cRynioAVAX6RSQ6WrNlINI9EfWAkUNfeLPPcnyrgFJWuUfWxe3PUtpg3MKCN G7axyjblirwaZGrch3EYtkmax4oikE11LrmyIdKvTDh3f1/5CGUAqZ5owsUKsG6Z9m6F 03GvqW02nnYbR+h9AOp9MknA87ewQY+6JS9KzFJVqlbge8RtLgtfcaMTgp9dA6HHRXx1 ZeFQ== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of jan.kiszka@siemens.com designates 194.138.37.40 as permitted sender) smtp.mailfrom=jan.kiszka@siemens.com; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=siemens.com Return-Path: Received: from gecko.sbs.de (gecko.sbs.de. [194.138.37.40]) by gmr-mx.google.com with ESMTPS id o10si679119lfg.12.2021.03.03.04.09.55 for (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 03 Mar 2021 04:09:55 -0800 (PST) Received-SPF: pass (google.com: domain of jan.kiszka@siemens.com designates 194.138.37.40 as permitted sender) client-ip=194.138.37.40; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of jan.kiszka@siemens.com designates 194.138.37.40 as permitted sender) smtp.mailfrom=jan.kiszka@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 gecko.sbs.de (8.15.2/8.15.2) with ESMTPS id 123C9sv0017281 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Wed, 3 Mar 2021 13:09:54 +0100 Received: from [139.22.114.127] ([139.22.114.127]) by mail2.sbs.de (8.15.2/8.15.2) with ESMTP id 123C4rjj023107; Wed, 3 Mar 2021 13:04:54 +0100 Subject: Re: Custom recipe, multiple machines for same arch To: Daniel Machon , "isar-users@googlegroups.com" References: From: Jan Kiszka Message-ID: <2a8fcac4-d6c1-637b-a1e1-54a8e1dbabd4@siemens.com> Date: Wed, 3 Mar 2021 13:04:53 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.7.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-TUID: sJAX/JH+Z8gm On 03.03.21 12:37, Daniel Machon wrote: > Hi, > >   > > Is there an elegant way to handle custom recipes, that are used in > multiple machines that target the same architecture. > > Currently when I try to execute a multi-machine build, it fails with: > */Detect multiple executions of ../* > > You can get around this by changing PN = /recipe-name/-${MACHINE} in > each custom recipe and IMAGE_INSTALL += /recipe-name/-${MACHINE} > > I am just wondering whether this is the best solution, or if there are > any alternatives? > Yes, you can share recipes across multiple configuration (multi-config). You will find examples of that in Isar itself and also in [1]. But this can easily cause false-sharing problems. To detect those, we installed an instrumentation that reported such a case in your setup. It basically detects if there are variables evaluated by the recipe that vary across the builds for different multi-config targets. The next thing then is to understand what makes the recipes specific to the machines and then resolve that. One way is building the recipes machine-specific, this is what you described above. But maybe there is also a more elegant way in your case. This is hard to answer generally, though. You may try to compare the task signatures of the different runs via bitbake-diffsigs which should visualize the varying vars. Jan -- Siemens AG, T RDA IOT Corporate Competence Center Embedded Linux