From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6452539580202614784 X-Received: by 10.223.160.153 with SMTP id m25mr993497wrm.3.1503360981141; Mon, 21 Aug 2017 17:16:21 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 10.25.169.130 with SMTP id s124ls665444lfe.36.gmail; Mon, 21 Aug 2017 17:16:20 -0700 (PDT) X-Received: by 10.46.13.18 with SMTP id 18mr2383591ljn.42.1503360980510; Mon, 21 Aug 2017 17:16:20 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1503360980; cv=none; d=google.com; s=arc-20160816; b=OuXAsVCTD+loULJ78u/zDegE+qbcqaqVAT+d9U03qEzF4cgrsJnH6JAjbru72eE/lk U1beHeg4HgCjQLkaB65NGtcNR2G8prQS2BgCmLueD5OP4EFjVl7Cuz1dY5/f3igbRYbX mAOXvMj/czzlRqiiWi1buXnv8le2UhjerqOD1l6DgVOCOFMaP6B+IM0j70JlplYdkJj/ iygDQQ3TrzdfdrkjNaqgGdydPBRFRFY4zkkk8uRuBp+EUdpgTQhPR/g1D+7zyAIAGEG5 11XEo8OSTL65sIB6YN6cU6dAfhqN8/qzORRJyf+kgNSJhQYkDjoZY6eRY2yLiGEwd07R LLVw== 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=FMN6haQ9lommR1IFlQh0GgINIUfHm/+FsnNp0ebir8I=; b=k9DMm+3CQWEyroXwnRjUbB3CsfAk6HikEemYi9YKyH2k6UWiwio3Q/YUNCbSfSuFsH APcDIlNEsL/Vb5xvufALALCWHcFBp4lhbyH19un2M+RcmlhzSgie38IoWhGeKD1tgxSb jnQkvYMAFuDJVkJNFrmT4ZXvxx5JVd7TsGFwh4MeysM612OHGg1pRprT6WtnPSJvqWgc jOMH0lGpnUn1fp2fx1WYrcXhHGimmsOZ1a5KBE9quYlhU+xli461yfpZNT+KJ+RrXql6 i4zhKo0gY5EhvlXP1wirnutN/uFbpsiUUNOUSkupWLoY5F0zcIhDqCxLcBoi0Dz8UHY8 skvw== 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 72si2982969wmo.9.2017.08.21.17.16.20 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 21 Aug 2017 17:16:20 -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 (dslb-088-067-177-003.088.067.pools.vodafone-ip.de [88.67.177.3]) (authenticated bits=0) by aqmola.ilbers.de (8.14.4/8.14.4/Debian-4+deb7u1) with ESMTP id v7M0GII0010744 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for ; Tue, 22 Aug 2017 02:16:19 +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 v7M0GDxo008315 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for ; Tue, 22 Aug 2017 02:16:13 +0200 Received: (from ibr@localhost) by yssyq.radix50.net (8.14.4/8.14.4/Submit) id v7M0GC3t008314 for isar-users@googlegroups.com; Tue, 22 Aug 2017 02:16:12 +0200 Date: Tue, 22 Aug 2017 02:16:12 +0200 From: Baurzhan Ismagulov To: isar-users@googlegroups.com Subject: Re: Why does Isar build multiple configs in one OUTDIR? Message-ID: <20170822001612.GO3711@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> <20170810142501.GA4053@yssyq.radix50.net> <64b4e93c-c615-dd2c-128d-46ca737f9649@siemens.com> <20170811182024.GB3896@yssyq.radix50.net> <26591538-251f-4882-1f73-d713391dc291@siemens.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <26591538-251f-4882-1f73-d713391dc291@siemens.com> User-Agent: Mutt/1.5.23 (2014-03-12) X-TUID: RDq0qrxugXHO On Sat, Aug 19, 2017 at 09:53:54AM -0400, Jan Kiszka wrote: > Theoretically, Isar could still build without multiconfig. But > practically, more and more information is now only in > meta-isar/conf/multiconfig, and one would has to copy that out into an > own local.conf (or a kas config). Good catch, thanks. Indeed, building with the default local.conf produces a working image, albeit the kernel / initrd is not extracted. https://github.com/ilbers/isar/issues/29 > But focusing on one method is fine, we should just avoid confusions > regarding the other. As multiconfig is relatively new in bitbake, many people are not familiar with it. Besides, local.conf would save people with one config the cumbersome multiconfig syntax. I think keeping local.conf working shouldn't cost too much effort -- in the worst case, the vars added to multiconfig should also be added to local.conf. Maybe we manage to come up with some standard customization file location without having to repeat ourselves. With kind regards, Baurzhan.