From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6452539580202614784 X-Received: by 10.46.80.88 with SMTP id v24mr1282222ljd.0.1502439253120; Fri, 11 Aug 2017 01:14:13 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 10.25.81.210 with SMTP id g79ls58920lfl.3.gmail; Fri, 11 Aug 2017 01:14:12 -0700 (PDT) X-Received: by 10.25.72.215 with SMTP id v206mr1675741lfa.28.1502439252623; Fri, 11 Aug 2017 01:14:12 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1502439252; cv=none; d=google.com; s=arc-20160816; b=GqXLjWoI6neit4J+xaUjBLSn0w61JOMzRmkjhhPBLQbG9xU+KuIJNPh9HAfvuFMldt WzeQfbxvv5CYo8TxQtm8BA4nUVpQ0pXJAO3jAMOEbefoHQgAER1BLxD1XFri2M5L0hjP jRRiD72sffXMxxjJg9oKwmkAjQ/MX/AKzwmQUhChqWPVTC4ixCc8fYcDuF+avjPeoRP3 VeS0x6JmuJnTRjpJIYXyKQ/wvEQVBtVJkfsutrfOkIdaE0QrcXCOl2rBv1BTSVY1AgFX ryO37B/NPxOcYKe/Z9F5f5r8QwE2GUAM3lzJ+FhZYhVnCGDzTwFJSd826sq3ue+GzYNu LFkQ== 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=g8Fo1WYADEmgVSNJqtpBbNjOQs0A7H2RmrtyX8SgFpA=; b=H/ZMHTWXiOmkfO17qnFZ8FTPfQ3LN1RlOQOm8n1WF9SXlxtqXiCnu0F1XFki4l2tao YHc+JoXwy0RLr6ZD3VBKVECMRigfIirw3QIQvdjcnmp5zikhKePZ7WVIOfYzzDMl6zQn qFzWxYNzU6omEjyz6RAc0QWFXRwUvpP2Xo/m8DnHie+At1vn0fgdrKbIif3ct/l+gCKw 78X93kGM4ybJ07ayNiyIi6MR5jePt2ypRBKcmcEzH/Oj1V8ICF+VcUDiZ835oIroKF8W HtwiYZJfp1Cm0C40bqcFiYvgLhTiY7Fd1Oo7DMMlTwX6+KxTA6cBGobYSPe28qHVJ5IR bI+Q== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=neutral (google.com: 192.35.17.2 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 thoth.sbs.de (thoth.sbs.de. [192.35.17.2]) by gmr-mx.google.com with ESMTPS id 72si23107wmo.9.2017.08.11.01.14.12 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 11 Aug 2017 01:14:12 -0700 (PDT) Received-SPF: neutral (google.com: 192.35.17.2 is neither permitted nor denied by best guess record for domain of henning.schild@siemens.com) client-ip=192.35.17.2; Authentication-Results: gmr-mx.google.com; spf=neutral (google.com: 192.35.17.2 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 thoth.sbs.de (8.15.2/8.15.2) with ESMTPS id v7B8ECeY027055 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Fri, 11 Aug 2017 10:14:12 +0200 Received: from md1em3qc ([139.25.68.40]) by mail2.siemens.de (8.15.2/8.15.2) with ESMTP id v7B8ECLL000537; Fri, 11 Aug 2017 10:14:12 +0200 Date: Fri, 11 Aug 2017 10:16:09 +0200 From: Henning Schild To: Baurzhan Ismagulov Cc: Subject: Re: Why does Isar build multiple configs in one OUTDIR? Message-ID: <20170811101609.7eb7a8ce@md1em3qc> In-Reply-To: <20170810142501.GA4053@yssyq.radix50.net> References: <20170810091059.4244e529@md1em3qc> <15dcbe16a70.27ac.034a6b0541ed39b7fb4e17f4ac219eaa@ilbers.de> <20170810141754.68624a32@md1em3qc> <20170810130951.GB3259@yssyq.radix50.net> <20170810155237.760cfa40@md1em3qc> <20170810142501.GA4053@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: A22MZv6BukKT Am Thu, 10 Aug 2017 16:25:02 +0200 schrieb Baurzhan Ismagulov : > On Thu, Aug 10, 2017 at 03:52:37PM +0200, Henning Schild wrote: > > > 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. > > ICH Plant Edition contains multiple cards that are armhf, use wheezy > but have different user-space applications. They share the same > buildchroot. Ok that is the example i asked about initially. Thanks! Henning > > > > 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. > > Maybe? Please specify how you suggest to build images for ICH WE and > PE. > > The fact is, the products are already layered and split in different > git repos. Apart from the fact that Isar predates kas and solves the > problem well: I'd use kas for cloning disparate repos (like the repo > tool in Android), not for build dir management. > > > > > What for? > > > > Simplicity, Elegance, Maintainability, Modularity ... ty > > After you specify your image building solution, please show how yours > is better in these regards. > > If you need only one arch + suite combination, you may still use > local.conf without multiconfig. > > And if you like, you may still layout your product to your taste and > use your preferred solution with stock Isar. What is exactly the > problem you are trying to address? Multiconfig doesn't take anything > away from you. Artifact reuse is in place within the same arch + > suite. > > > With kind regards, > Baurzhan. >