From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6452539580202614784 X-Received: by 10.129.209.12 with SMTP id w12mr7621926ywi.91.1502375113427; Thu, 10 Aug 2017 07:25:13 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 10.36.77.78 with SMTP id l75ls7939739itb.6.canary-gmail; Thu, 10 Aug 2017 07:25:13 -0700 (PDT) X-Received: by 10.36.67.5 with SMTP id s5mr7544974itb.28.1502375113035; Thu, 10 Aug 2017 07:25:13 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1502375113; cv=none; d=google.com; s=arc-20160816; b=sWXWiYaETKMO79Fch/1ngINvuAelJpM+Jo7zti7DI6Kx405Vgoq1IeC+hIWjg5tqFs BagBhp0P0B3dEpfjuvfgist5LH54yTVP4/n8MyLCz2AkqtEEeBDAB4ri+YeUqQAqklTR c47aFzvnFDA3m2hUxQTXQIyWW6AJXoTK6z4bNXJwKA6H8JUA9N28uuvragELTQB0wEC4 N3bFN4safia5QFRKkFt7cuhG9MOkoSgscl4U3/M3QlrEgsdBiaAQiufs9j9hUr4PhUua U6fj50ud16o9Yv68hfO7v05FvACcYNXi8XQT54jOB0gToq3kfWPYdyWt6KVZmWExlrhk pbzA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=user-agent:in-reply-to:content-disposition:mime-version:references :mail-followup-to:message-id:subject:to:from:date :arc-authentication-results; bh=vZBqexONJPIm/29fZ4P/7XSX0Nxj84q77lXKL+ZeZMs=; b=Krt/tEBkOZAxEP90pgBroNAF81lFhHVjlT2RoFiIv+2ZFoIPkRonfeE7FmETlLXByq hEtMZFh2BY8/Ctf9z1pjm7nE+2PQjfhWOUu2ezKHrzNhqXCutZH9fPjewmqDmGKclfpd ltnRxKty+9zgrIv0npGa7/u2vEAG2i/8c3nDiJg9UueCp7jjjV2u/+tC/IUWoJ8sabZn w0y4lmMGJxXRPJs35P06/M5a9p23/f+10hKRId+6E+qqEDqCk1F/dPj0NRyy+LjnNnc+ psFtI+hcTva79xflRMkYzfAiRoJQSxBGfTIInCSJPRiesQUlz6m3MJuAJ/SsT63/u5ke LOSQ== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=neutral (google.com: 85.214.62.211 is neither permitted nor denied by best guess record for domain of ibr@radix50.net) smtp.mailfrom=ibr@radix50.net Return-Path: Received: from aqmola.ilbers.de (aqmola.ilbers.de. [85.214.62.211]) by gmr-mx.google.com with ESMTPS id o128si239701itc.1.2017.08.10.07.25.12 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 10 Aug 2017 07:25:12 -0700 (PDT) Received-SPF: neutral (google.com: 85.214.62.211 is neither permitted nor denied by best guess record for domain of ibr@radix50.net) client-ip=85.214.62.211; Authentication-Results: gmr-mx.google.com; spf=neutral (google.com: 85.214.62.211 is neither permitted nor denied by best guess record for domain of ibr@radix50.net) smtp.mailfrom=ibr@radix50.net Received: from yssyq.radix50.net ([206.167.44.205]) (authenticated bits=0) by aqmola.ilbers.de (8.14.4/8.14.4/Debian-4+deb7u1) with ESMTP id v7AEP822006637 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for ; Thu, 10 Aug 2017 16:25:10 +0200 Received: from yssyq.radix50.net (localhost [127.0.0.1]) by yssyq.radix50.net (8.14.4/8.14.4/Debian-8) with ESMTP id v7AEP2eo005529 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for ; Thu, 10 Aug 2017 16:25:02 +0200 Received: (from ibr@localhost) by yssyq.radix50.net (8.14.4/8.14.4/Submit) id v7AEP2pa005528 for isar-users@googlegroups.com; Thu, 10 Aug 2017 16:25:02 +0200 Date: Thu, 10 Aug 2017 16:25:02 +0200 From: Baurzhan Ismagulov To: isar-users@googlegroups.com Subject: Re: Why does Isar build multiple configs in one OUTDIR? Message-ID: <20170810142501.GA4053@yssyq.radix50.net> Mail-Followup-To: isar-users@googlegroups.com References: <20170810091059.4244e529@md1em3qc> <15dcbe16a70.27ac.034a6b0541ed39b7fb4e17f4ac219eaa@ilbers.de> <20170810141754.68624a32@md1em3qc> <20170810130951.GB3259@yssyq.radix50.net> <20170810155237.760cfa40@md1em3qc> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170810155237.760cfa40@md1em3qc> User-Agent: Mutt/1.5.23 (2014-03-12) X-TUID: MYRswAYb0k3x 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. > > 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.