From: Andre McCurdy <armccurdy@gmail.com>
To: Ming Liu <liu.ming50@gmail.com>
Cc: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH V2] bitbake.conf: add BB_CURRENT_MC to OVERRIDES
Date: Mon, 11 Jun 2018 16:15:22 -0700 [thread overview]
Message-ID: <CAJ86T=X_BFLzGB4PDKSOJR3Boiv+gQvTN-3D+d+tk=Otw7iwew@mail.gmail.com> (raw)
In-Reply-To: <1528716867-20270-1-git-send-email-liu.ming50@gmail.com>
On Mon, Jun 11, 2018 at 4:34 AM, <liu.ming50@gmail.com> wrote:
> From: Ming Liu <liu.ming50@gmail.com>
>
> This is useful when the users want different variables/tasks when using
> multiconfig.
Isn't the idea of multiconfig to select between configurations which
already fully define all necessary over-rides?
If a particular multiconfig build needs a custom over-ride then the
multiconfig can append to OVERRIDES (or MACHINEOVERRIDES etc, as
appropriate) directly.
ie to avoid confusion isn't it good if building with a multiconfig
enabled is always equivalent to building with the contents of the
multiconfig file copied directly in local.conf?
> Signed-off-by: Ming Liu <liu.ming50@gmail.com>
> ---
> meta/conf/bitbake.conf | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
> index 3b2ef9f..0c803d5 100644
> --- a/meta/conf/bitbake.conf
> +++ b/meta/conf/bitbake.conf
> @@ -731,7 +731,7 @@ DISTRO_NAME ??= "OpenEmbedded"
> # And finally '<foo>_forcevariable' overrides any standard variable, with the highest priority.
> # This works for functions as well, they are really just variables.
> #
> -OVERRIDES = "${TARGET_OS}:${TRANSLATED_TARGET_ARCH}:pn-${PN}:${MACHINEOVERRIDES}:${DISTROOVERRIDES}:${CLASSOVERRIDE}${LIBCOVERRIDE}:forcevariable"
> +OVERRIDES = "${TARGET_OS}:${TRANSLATED_TARGET_ARCH}:pn-${PN}:${MACHINEOVERRIDES}:${DISTROOVERRIDES}:${CLASSOVERRIDE}${LIBCOVERRIDE}:mc-${BB_CURRENT_MC}:forcevariable"
> LIBCOVERRIDE ?= ""
> CLASSOVERRIDE ?= "class-target"
> DISTROOVERRIDES ?= "${@d.getVar('DISTRO') or ''}"
> --
> 2.7.4
>
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
next prev parent reply other threads:[~2018-06-11 23:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-11 11:34 [PATCH V2] bitbake.conf: add BB_CURRENT_MC to OVERRIDES liu.ming50
2018-06-11 23:15 ` Andre McCurdy [this message]
2018-06-12 11:43 ` Ming Liu
2018-06-12 17:49 ` Andre McCurdy
2018-06-13 8:39 ` Ming Liu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJ86T=X_BFLzGB4PDKSOJR3Boiv+gQvTN-3D+d+tk=Otw7iwew@mail.gmail.com' \
--to=armccurdy@gmail.com \
--cc=liu.ming50@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.