From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6452539580202614784 X-Received: by 10.28.141.4 with SMTP id p4mr680760wmd.20.1502373042524; Thu, 10 Aug 2017 06:50:42 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 10.28.134.141 with SMTP id i135ls2763838wmd.10.canary-gmail; Thu, 10 Aug 2017 06:50:42 -0700 (PDT) X-Received: by 10.223.183.47 with SMTP id l47mr877165wre.26.1502373042242; Thu, 10 Aug 2017 06:50:42 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1502373042; cv=none; d=google.com; s=arc-20160816; b=T9mFxcdJfpw6JzaQV13YPFiGT/ouiigLtedlQ1aHAAM8jybj8pYkRVvakxlwhON2RX nB6nYu+bzaVjx7/N9OegCFtXeLupU7EDC0E5knWvNOd8wQxN+dqwNbDYzK4CdW6szxO3 HWoAJM93N1tBHgKGa7lXCdCdlMAgpiwvnQX4JM0jkwMY2JMo0xpXSo+DVKMQ6bUM51BR ZCiIc3OpsDJRhPi/KLkuiH2kBDdTM9lsOrM5DJpUAqAeq3yfdiRk1VV6HxkEOk66StsU nZZJBUfUxqby8t/LhM807mATrB0iiWvrYyH/cmznMr/TjnUvuAWg3COlAkPmaBcS+SMh RssA== 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:arc-authentication-results; bh=VLJzx1uQZCvGm493Gx0636jfOYgbiPcVA7UchzBg/zk=; b=uWY/fJO4ywSqo3WH9A7ZPKStDOFxv79ha33UwRjO6bm53KycqpKiBLUACBdQdHyb/w I7nTDaMg12u+EgrlBXJQGQ4XhHosFdGr+9Px7XP1mzT+CCB9gNKiuYoTpkR5dXRsj6N6 DKlyCelrXCFZux6A9uBRewy8qRqJhc48OwaLivaq/w94IdUa3RhQZYTPH1GZx0z57T8a oEBgJ6Y7l7UFwhmmJDiENJfVY/W81EPEWM32YLelmxM3h/wa8QJ55agtW27osJSVvUeV 15fuSzvdHfsSFfg+SXb2EmOZX8aYEl79V6Hj02yVtOqX0WqICPjecb+C4QUdpXfPe1As MVZQ== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=neutral (google.com: 192.35.17.28 is neither permitted nor denied by best guess record for domain of henning.schild@siemens.com) smtp.mailfrom=henning.schild@siemens.com Return-Path: Received: from goliath.siemens.de (goliath.siemens.de. [192.35.17.28]) by gmr-mx.google.com with ESMTPS id b125si1061275wmc.1.2017.08.10.06.50.42 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 10 Aug 2017 06:50:42 -0700 (PDT) Received-SPF: neutral (google.com: 192.35.17.28 is neither permitted nor denied by best guess record for domain of henning.schild@siemens.com) client-ip=192.35.17.28; Authentication-Results: gmr-mx.google.com; spf=neutral (google.com: 192.35.17.28 is neither permitted nor denied by best guess record for domain of henning.schild@siemens.com) smtp.mailfrom=henning.schild@siemens.com Received: from mail2.siemens.de (mail2.siemens.de [139.25.208.11]) by goliath.siemens.de (8.15.2/8.15.2) with ESMTPS id v7ADof1j002659 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Thu, 10 Aug 2017 15:50:41 +0200 Received: from md1em3qc ([139.25.68.40]) by mail2.siemens.de (8.15.2/8.15.2) with ESMTP id v7ADofaF011492; Thu, 10 Aug 2017 15:50:41 +0200 Date: Thu, 10 Aug 2017 15:52:37 +0200 From: Henning Schild To: Baurzhan Ismagulov Cc: Subject: Re: Why does Isar build multiple configs in one OUTDIR? Message-ID: <20170810155237.760cfa40@md1em3qc> In-Reply-To: <20170810130951.GB3259@yssyq.radix50.net> References: <20170810091059.4244e529@md1em3qc> <15dcbe16a70.27ac.034a6b0541ed39b7fb4e17f4ac219eaa@ilbers.de> <20170810141754.68624a32@md1em3qc> <20170810130951.GB3259@yssyq.radix50.net> X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.31; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-TUID: Fm5CKFRqgXxt Am Thu, 10 Aug 2017 15:09:51 +0200 schrieb Baurzhan Ismagulov : > On Thu, Aug 10, 2017 at 02:17:54PM +0200, Henning Schild wrote: > > > > The only reuse of a build step i see at the moment is the > > > > git-clone of Isar itself. Where are the gains that justify the > > > > complexity? If there is a good reason, that i did understand > > > > yet, please answer to this point and you can stop reading > > > > here. > > > > Please answer this key question, with examples. > > Alex did. Well I did not understand it. And i still do not. > Industry Control Hub Workshop Edition is armhf and uses jessie. > Industry Control Hub Plant Edition is armhf and uses wheezy. > They share the same user-space application. So two complete rootfs s that share one application? And they probably only share the source and recipe to build it. I still do not see where these two share any (intermediate) build results, sorry. > The application is updated. > Both models are released. > You build them from the same build dir. ? > This comes from real life and this has been the key requirement on > Isar from the very beginning. The customer wants to build all > artifacts with the same release cycle in one step. > > If we returned to the pre-multiconfig way of having separate build > dirs, automating building all products in the repo would require > gluing those two steps together. How? Shell with sed patching of > local.conf? Bitbake Layering. Maybe combined with git submodules or kas. > What for? Simplicity, Elegance, Maintainability, Modularity ... ty > Isar *is* the single-stop glue. Ok. Understood but not convinced. Henning > With kind regards, > Baurzhan. >