From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6573322325979037696 X-Received: by 2002:a1c:5b0b:: with SMTP id p11-v6mr1085133wmb.11.1530521891180; Mon, 02 Jul 2018 01:58:11 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 2002:adf:eb4d:: with SMTP id u13-v6ls3994959wrn.0.gmail; Mon, 02 Jul 2018 01:58:10 -0700 (PDT) X-Google-Smtp-Source: AAOMgpf56WQKobiHEFF0VR9f9Qf98Y/pWAiqx9p3iRcl73UE/2lyfqVCHuZ/VKYgKolM2/ikF6dU X-Received: by 2002:adf:ce85:: with SMTP id r5-v6mr46000wrn.22.1530521890780; Mon, 02 Jul 2018 01:58:10 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1530521890; cv=none; d=google.com; s=arc-20160816; b=CPPnKbXpegbKXa/BxTKCaNVH5arqfwFH+ZlLkEtlrbbEXY56BoRBWbmLLS4PE5Tju7 T3DGfPpwYYB+clJ3wyfeTk7D1jv9iWWtlZJRhm3zke/m3NK5BIyeSnsyE9oWUeZjqGp+ m9b6jlsjEOQMbX/J9oBczFgQ15kLD9vpwRW5DWqWgKAudvBGhbnwaYcv3IMpcs5HC7si GowHtcUkZDL3B1q+e0Pt7pzs9GzHEsvo5B62ao4x+WACP34dJEDSID7sW4Dhq5MSL2l/ Tv2ol8Mj47rMpiaOhZBNpnol4ZcKdB8ZjSRekzrRhce1tou4qxJ44wXmVbkqXyQsxV49 XUjw== 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=uLVIJAXUKBAQGf80rsbx/JndArEIa5O/+h7x0h2MWs4=; b=krWoR2opba0C8cODsfZtWgQe3i5zJi+UPuFmaVomdIbguMvtsYC2yZyBjew/BNq8iZ wvxWc66YC2NmR43aIlLNITsFK75/MgPheQBYjT+/tuMGt8kEZaQ+psa/d8HppVZg52qZ Yy7q22ZemH/88U/jcjka0jQ6YCwYCIj0KpDUkzjMeAd0kq7AbNys+Zfk1go+kUENEo9d NKRC7jqYvBvMrdrB68tukj6QyBrS2Dt/htDd1djm4CdQvTJVqFMV8VIaKBPT232VSlOh kM5Q6CONeh5ZcRCycaxp3bVqazaQVydQcP7KpY4fEji+LVF4koWcCK1cN7910C3T9SGX mbCg== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of henning.schild@siemens.com designates 192.35.17.2 as permitted sender) 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 d18-v6si526748wrj.3.2018.07.02.01.58.10 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 02 Jul 2018 01:58:10 -0700 (PDT) Received-SPF: pass (google.com: domain of henning.schild@siemens.com designates 192.35.17.2 as permitted sender) client-ip=192.35.17.2; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of henning.schild@siemens.com designates 192.35.17.2 as permitted sender) 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 w628wAvK010671 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Mon, 2 Jul 2018 10:58:10 +0200 Received: from md1pvb1c.ad001.siemens.net (md1pvb1c.ad001.siemens.net [139.25.68.40]) by mail2.siemens.de (8.15.2/8.15.2) with ESMTP id w628wAmQ017587; Mon, 2 Jul 2018 10:58:10 +0200 Date: Mon, 2 Jul 2018 10:58:09 +0200 From: Henning Schild To: Jan Kiszka Cc: isar-users Subject: Re: Multiconfig woes Message-ID: <20180702105809.02040e1f@md1pvb1c.ad001.siemens.net> In-Reply-To: <94817738-b2ca-7747-dc1c-c002d765ce75@web.de> References: <20180702101009.7891fd76@md1pvb1c.ad001.siemens.net> <94817738-b2ca-7747-dc1c-c002d765ce75@web.de> X-Mailer: Claws Mail 3.15.0-dirty (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: O2+dJgLBrGmk Am Mon, 2 Jul 2018 10:15:19 +0200 schrieb Jan Kiszka : > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 2018-07-02 10:10, Henning Schild wrote: > > Am Sun, 1 Jul 2018 20:47:38 +0200 schrieb Jan Kiszka > > : > > > >> Hi, > >> > >> I'm trying to model building different images for different > >> machines - but for the same architecture. That promises the reuse > >> of common packages when everything is modeled properly (the > >> kernel, e.g., will be configured to enable that). But it also > >> exposes some ugliness. > >> > >> These are my targets so far: > >> > >> multiconfig:machine1-distro:image > >> multiconfig:machine2-distro:image > >> > >> Both machines will share DISTRO_ARCH but will have different > >> MACHINE variables, obviously. The image recipe will be widely > >> identical, except for some machine-specific packages, selected > >> by "package-${MACHINE}". So far so good. > >> > >> But now we have the same image target in the same distro-arch > >> work folder, and that clashes. To resolve that, I also need > >> change PN in the image recipe to "image-${MACHINE}", and that > >> results in the following targets: > >> > >> multiconfig:machine1-distro:image-machine1 > >> multiconfig:machine2-distro:image-machine1 > >> > >> Kind of ugly, having the machine ID twice in this target > >> specification. Is there any better way to model such a scenario? > > > > I would try to model that in another image. Just like > > isar-image-debug extends isar-image-base. If you also need to > > remove stuff you might need one common include for both. > > That is exactly what I wrote above: isar-image-machine1, > isar-image-machine2. But, combined with the config specification, you > then encode the machine twice. Well you could use any string in the image-name, as long as they differ. Using the machine again just makes things more obvious. If you still want different names there is always PROVIDES, or a recipe that DEPENDS on both images. Henning > Jan > -----BEGIN PGP SIGNATURE----- > > iF0EARECAB0WIQTKX4wA9fvIVGYBbICK1KxveuXnFAUCWznfFAAKCRCK1KxveuXn > FGk8AJ4hBGjuG0M1eJDS/MhLUyFrGPGelQCfWPkkbnD2PuFeFsWjDtr/1mUdNWI= > =d1Hc > -----END PGP SIGNATURE-----