From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wr1-f51.google.com (mail-wr1-f51.google.com [209.85.221.51]) by mail.openembedded.org (Postfix) with ESMTP id 34EB860C96 for ; Wed, 5 Feb 2020 14:02:03 +0000 (UTC) Received: by mail-wr1-f51.google.com with SMTP id c9so2853037wrw.8 for ; Wed, 05 Feb 2020 06:02:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=RajyAy+4pAQ/ChCmkcwzK5+AQLacHrxPa4TSJPcDip0=; b=nfsBhzOoY7EyYnGwGU97ncrYuEA1RXl5Sdnv45TTQi3riuBtysVUzyNBVOzE78ad8F ZvFY/oMtEAKzsoZrhgIUnaX1oQqnnQlO4GoX9ItPQa/5Sa1p1o5S9+iiRgMSNRecwvlC aJyXRtcMNh1ild+0QOGs7kBT+8Icb2d0bxflxGJbrlBe6KrYCWLmOoqBZrc5Cs0N1MD+ vMZQgtC0mhhIYG4QzuXYvme9MAhfz2u2JlLf8+a1QcbbxD3Ec8Px0+kd0pDPt75rxD/y 0f1pfT8fF4J+qq/moxMDz/9lKuHyhQacrp00sMSHKvbfVOyV6OjyDNs46ffXmilolhax ar6w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=RajyAy+4pAQ/ChCmkcwzK5+AQLacHrxPa4TSJPcDip0=; b=QAtYk21g3QW7xGMRtsLm5ESYuik53udRA3DQWsgsWjgOJ0x/K/R+uPbRxXl2d41YHl oZObS18GzwRzkAYuPfL4EH4EiUEHtxZuA5C1EyVM0rV9EU/v+6OH/Spq6d9m9t1abcmK T39iH5thtMZY0AVNTRFQlLVSTF6kPjOJcM6WcS+fXtMahIbkG0bFZWsVYybVBnFC0z8m JOTWBmjW4S4Kabw2Q+sHvOggLMU36yUGg5d8Bd+mZ9Jz0kCU81kTDr+QEMuzLJC7w6AA HD4NRrFmCwFbcZmoMxrwp7nW/fcc35KVgfILQej3jiexe1Q/Rpy5HNtIlRW5B3T4LDs0 VFDQ== X-Gm-Message-State: APjAAAW5bV/JWnhKHR5tlwfUgrHFqtS36kbXDqE0l6GY8OxfuJZ68+go 1uRST3dsRWu5crOsmswRecSWHvwioxkE2Qz/Ag4kgw== X-Google-Smtp-Source: APXvYqymEWQbH50XVRtLbkmQS40fetzKIp4xut6+SVlZ1A66kz9hxeVmFNM3lWhW9cbILFbse92OSSoJbdi4d4+SBO0= X-Received: by 2002:a5d:4481:: with SMTP id j1mr28168045wrq.348.1580911323815; Wed, 05 Feb 2020 06:02:03 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Joshua Watt Date: Wed, 5 Feb 2020 08:01:50 -0600 Message-ID: To: "Robert P. J. Day" Cc: BitBake developer list Subject: Re: confused by multiconfig explanation in bitbake manual X-BeenThere: bitbake-devel@lists.openembedded.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Patches and discussion that advance bitbake development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Feb 2020 14:02:03 -0000 Content-Type: multipart/alternative; boundary="000000000000e0a787059dd499b1" --000000000000e0a787059dd499b1 Content-Type: text/plain; charset="UTF-8" On Wed, Feb 5, 2020, 7:58 AM Robert P. J. Day wrote: > On Wed, 5 Feb 2020, Joshua Watt wrote: > > > > > > > On Wed, Feb 5, 2020, 4:26 AM Robert P. J. Day > wrote: > > > > i've never defined a multiconfig build, but this section > explaining > > it in the BB user manual seems confusing: > > > > ///// start > > > > The following statement in the local.conf file both enables > BitBake to > > perform multiple configuration builds and specifies the two extra > > multiconfigs: > > > > BBMULTICONFIG = "target1 target2" > > > > Once the target configuration files are in place and BitBake has > been > > enabled to perform multiple configuration builds, use the following > > command form to start the builds: > > > > $ bitbake [mc:multiconfigname:]target > [[[mc:multiconfigname:]target] ... ] > > > > Here is an example for two extra multiconfigs: target1 and target2: > > > > $ bitbake mc::target mc:target1:target mc:target2:target > > > > ///// end > > > > i don't understand the "mc::target" part of that last command, > as it > > does not seem to be compatible with the definition of the general > form > > of the command just above that, specifically: > > > > $ bitbake [mc:multiconfigname:]target ... > > > > can someone clarify this? > > > > > > "target" is the recipe you want to build, just as you would have > specified if you were not using a "mc:multiconfig:" > > prefix. For examples: > > > > # build core-image-minimal > > bitbake mc:my-mulitconfig:core-image-minimal > > > > # build BusyBox > > bitbake mc:my-mulitconfig:busybox > > > my confusion was with the example that started with the two colons: > > $ bitbake mc::target ... > > the manual doesn't seem to explain the meaning of that "::" bit. > Ah sorry. I'm not sure. I've not seen that used much, if ever. Based on the code, I would assume that's equivalent to just " bitbake target", but I'm not positive. > rday --000000000000e0a787059dd499b1 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Wed, Feb 5, 2020, 7:58 AM Robert P. J. Day <rpjday@crashcourse.ca> wrote:
On Wed, 5 Feb 2020, Joshua Watt wrot= e:

>
>
> On Wed, Feb 5, 2020, 4:26 AM Robert P. J. Day <rpjday@crashcours= e.ca> wrote:
>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0 i've never defined a multiconfig = build, but this section explaining
>=C2=A0 =C2=A0 =C2=A0 =C2=A0it in the BB user manual seems confusing: >
>=C2=A0 =C2=A0 =C2=A0 =C2=A0///// start
>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0The following statement in the local.conf fi= le both enables BitBake to
>=C2=A0 =C2=A0 =C2=A0 =C2=A0perform multiple configuration builds and sp= ecifies the two extra
>=C2=A0 =C2=A0 =C2=A0 =C2=A0multiconfigs:
>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0 =C2=A0 =C2=A0BBMULTICONFIG =3D "= target1 target2"
>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0Once the target configuration files are in p= lace and BitBake has been
>=C2=A0 =C2=A0 =C2=A0 =C2=A0enabled to perform multiple configuration bu= ilds, use the following
>=C2=A0 =C2=A0 =C2=A0 =C2=A0command form to start the builds:
>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0 =C2=A0 =C2=A0$ bitbake [mc:multiconfi= gname:]target [[[mc:multiconfigname:]target] ... ]
>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0Here is an example for two extra multiconfig= s: target1 and target2:
>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0 =C2=A0 =C2=A0$ bitbake mc::target mc:= target1:target mc:target2:target
>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0///// end
>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0 i don't understand the "mc::= target" part of that last command, as it
>=C2=A0 =C2=A0 =C2=A0 =C2=A0does not seem to be compatible with the defi= nition of the general form
>=C2=A0 =C2=A0 =C2=A0 =C2=A0of the command just above that, specifically= :
>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0 =C2=A0 =C2=A0 $ bitbake [mc:multiconf= igname:]target ...
>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0can someone clarify this?
>
>
> "target" is the recipe you want to build, just as you would = have specified if you were not using a "mc:multiconfig:"
> prefix. For examples:
>
> =C2=A0# build core-image-minimal
> =C2=A0bitbake mc:my-mulitconfig:core-image-minimal
>
> =C2=A0# build BusyBox
> =C2=A0bitbake mc:my-mulitconfig:busybox
>
=C2=A0 my confusion was with the example that started with the two colons:<= br>
=C2=A0 $ bitbake mc::target ...

the manual doesn't seem to explain the meaning of that "::" b= it.

Ah sorry. I'm not sure. I've not seen that used much, if ever.

Based on the code, I woul= d assume that's equivalent to just " bitbake target", but I&#= 39;m not positive.


rday
--000000000000e0a787059dd499b1--