From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6452539580202614784 X-Received: by 10.28.96.194 with SMTP id u185mr1279467wmb.26.1502383044122; Thu, 10 Aug 2017 09:37:24 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 10.28.193.205 with SMTP id r196ls2129890wmf.13.canary-gmail; Thu, 10 Aug 2017 09:37:23 -0700 (PDT) X-Received: by 10.28.176.7 with SMTP id z7mr10491wme.2.1502383043768; Thu, 10 Aug 2017 09:37:23 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1502383043; cv=none; d=google.com; s=arc-20160816; b=qEkE10z+wnDkuhufHQ7HUFpTvIG6KS1q5utgMS+gKY7Fei9+7nMqLmD8flZa8cNJ5a 5+U7fARh3rjD8Ql31GjIrsmxrmoX2OFvCEFtwo/MoZl+SoZa7vUH5Mxdpj1PG7O7sQF2 iWpqdtfjhnvIaZ1cfy3mihfRG+0ci6T8tpHchZ9irKCcUS03Vst0ytKhPgd50xGMdifC cjerEznPduprG4mxrSmcM9flUAjy6qPXDqPV4+sXwwQdQkPWKJyMdqEPY2ddSuHdFpd8 iYsGMJbybCq7AEWT6cKAfizM+IZZyf/6LaOSXTyB5uRX4D8jSQBCK8vMpJsAToAql34V FRcw== 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 :arc-authentication-results; bh=0mVWt8D3m5FqxKjyebFCkeHez1FW5sQIIIxQqIOYet8=; b=oTMWyYMEgRP+a0tQ2NMCdAjTKXjjEwEhbLEP0z1f8LBemJjFowoj26P0Iv+lySShup 2PEQ60bQ5uJzUpK5unxFDYPjLQhzffKfxwThfrZH+G2OBYniGLmRjxznbYhOuIMO3Z9F 4jO0y5kYt6KMIOLQJuTH7KRtG1bYqSCd1tbUEBqXdtHoJJugBno5Dw0bsO5NWDvKYtBI uly3t4ktDglQxWju+fk1dq+/PlQHUxOJn+hBYyi4lkEAuHc5SBfNJxfJpbdheNlqPxDS isXsJgv7OZxFx9Tilri7tlKpj1pyx3BQUPGB7DZJ/+q5yOnwwSSCg5D1jOHBnSiyngcD I3lg== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=neutral (google.com: 192.35.17.14 is neither permitted nor denied by best guess record for domain of jan.kiszka@siemens.com) smtp.mailfrom=jan.kiszka@siemens.com Return-Path: Received: from david.siemens.de (david.siemens.de. [192.35.17.14]) by gmr-mx.google.com with ESMTPS id j199si557352wmj.4.2017.08.10.09.37.23 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 10 Aug 2017 09:37:23 -0700 (PDT) Received-SPF: neutral (google.com: 192.35.17.14 is neither permitted nor denied by best guess record for domain of jan.kiszka@siemens.com) client-ip=192.35.17.14; Authentication-Results: gmr-mx.google.com; spf=neutral (google.com: 192.35.17.14 is neither permitted nor denied by best guess record for domain of jan.kiszka@siemens.com) smtp.mailfrom=jan.kiszka@siemens.com Received: from mail2.siemens.de (mail2.siemens.de [139.25.208.11]) by david.siemens.de (8.15.2/8.15.2) with ESMTPS id v7AGbNU1012909 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Thu, 10 Aug 2017 18:37:23 +0200 Received: from md1f2u6c.ww002.siemens.net ([139.22.56.223]) by mail2.siemens.de (8.15.2/8.15.2) with ESMTP id v7AGbLwn030372 for ; Thu, 10 Aug 2017 18:37:22 +0200 Subject: Re: Why does Isar build multiple configs in one OUTDIR? 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> <20170810142501.GA4053@yssyq.radix50.net> From: Jan Kiszka Message-ID: <64b4e93c-c615-dd2c-128d-46ca737f9649@siemens.com> Date: Thu, 10 Aug 2017 12:37:01 -0400 User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); de; rv:1.8.1.12) Gecko/20080226 SUSE/2.0.0.12-1.1 Thunderbird/2.0.0.12 Mnenhy/0.7.5.666 MIME-Version: 1.0 In-Reply-To: <20170810142501.GA4053@yssyq.radix50.net> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-TUID: l83Qu23wuPp6 On 2017-08-10 10:25, Baurzhan Ismagulov wrote: >>> 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. kas manages config dependencies that are under the same release regime in a single file. It also provides a clean, archiveable build environment, which is even more important with OE. If your production generates multiple variants from a single release, there is surely a value in exploiting the new multiconfig feature of bitbake. It's an optimization that can save a hand full of lines in your CI script and likely quite a bit cycles of your CI server. I see it as an added value. But as Isar is already wrapped around it, no longer works without it (because that would mean duplicate maintenance), we have to make sure to support it, including a better support in kas. Jan -- Siemens AG, Corporate Technology, CT RDA ITP SES-DE Corporate Competence Center Embedded Linux