Yes, that is true, but then I will need have a mc-default override set in
local.conf any way, since I need distinguish the build for all
multiconfigs, that makes me think it'd better to have a single
mc-${BB_CURRENT_MC} set in OVERRIDES.
//Ming Liu
2018-06-12 19:49 GMT+02:00 Andre McCurdy :
> On
On Tue, Jun 12, 2018 at 4:43 AM, Ming Liu wrote:
> Hi, Andre:
> The reason for needing this multiconfig to be in OVERRIDES, for me, is the
> scenario that I have one recipe but some variables/tasks in it are different
> for multiconfig, for instance:
>
> do_install-mc-default () {}
>
> do_install-
Hi, Andre:
The reason for needing this multiconfig to be in OVERRIDES, for me, is the
scenario that I have one recipe but some variables/tasks in it are
different for multiconfig, for instance:
do_install-mc-default () {}
do_install-mc-foo() {}
and I do not want split them into several almost sa
On Mon, Jun 11, 2018 at 4:34 AM, wrote:
> From: Ming Liu
>
> 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 bu
From: Ming Liu
This is useful when the users want different variables/tasks when using
multiconfig.
Signed-off-by: Ming Liu
---
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 1006
