From: "Khem Raj" <raj.khem@gmail.com>
To: Rahul Chauhan <rahulchauhankitps@gmail.com>, poky@lists.yoctoproject.org
Subject: Re: [poky] Need suggestion to handle COMBINED_FEATURES variable.
Date: Wed, 18 May 2022 08:58:25 -0700 [thread overview]
Message-ID: <e84bba5e-3d55-61e7-4809-70ff3960df51@gmail.com> (raw)
In-Reply-To: <iXLe.1652882488907922335.H4ri@lists.yoctoproject.org>
On 5/18/22 7:01 AM, Rahul Chauhan wrote:
> Hi Team,
> I need one suggestion.
>
> As we know wifi is the default distro feature.
> meta/conf/distro/include/default-distrovars.inc
> <https://git.yoctoproject.org/poky/tree/meta/conf/distro/include/default-distrovars.inc> (this
> file add the DISTRO_FEATURES_DEFAULT)
>
> packagegroup-base-wifi is dependent on COMBINED_FEATURES wifi.
>
> ${@bb.utils.contains('COMBINED_FEATURES', 'wifi',
> 'packagegroup-base-wifi', '',d)} \
>
>
> I don't want to include*packagegroup-base-wifi* package group in my build.
>
> One way I can use DISTRO_FEATURES_remove = "wifi" in my distro.
Thats perhaps ok. poky distro config is a template that is meant to
serve as a reference. Ideally you should be defining your own distro
config in this case derivided from poky.conf and set the DISTRO_FEATURES
that suites your usecase.
>
> Second thing I can use COMBINED_FEATURES_remove = "wifi".
> But here my question is if I am using COMBINED_FEATURES_remove where is
> the ideal place to keep this variable.
> Or suggest me what is the ideal way to remove the combined feature from
> the build. (I dont't want to keep it in local.conf file)
> Thanks in advance.
> Rahul Chauhan
>
>
>
>
next prev parent reply other threads:[~2022-05-18 15:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-18 14:01 Need suggestion to handle COMBINED_FEATURES variable Rahul Chauhan
2022-05-18 15:58 ` Khem Raj [this message]
2022-05-18 16:30 ` Rahul Chauhan
2022-05-18 16:33 ` [poky] " Khem Raj
2022-05-18 16:47 ` Rahul Chauhan
2022-05-18 17:07 ` [poky] " Khem Raj
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=e84bba5e-3d55-61e7-4809-70ff3960df51@gmail.com \
--to=raj.khem@gmail.com \
--cc=poky@lists.yoctoproject.org \
--cc=rahulchauhankitps@gmail.com \
/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.