All of lore.kernel.org
 help / color / mirror / Atom feed
From: Uwe Geuder <jrswdnan22@snkmail.com>
To: yocto@yoctoproject.org
Subject: Re: so how does PACKAGECONFIG_remove really work?
Date: Fri, 09 Nov 2018 17:01:58 +0200	[thread overview]
Message-ID: <87wopmz449.fsf@snkmail.com> (raw)
In-Reply-To: <CAJTo0Lai9bbJeTgtwOvwB_jmNtfMGLj1PP2ywQdzee6ugNELaw@mail.gmail.com>

On Fri, Nov 9, 2018 at 4:41 PM Burton, Ross ross.burton-at-intel.com  wrote:
>
> On Fri, 9 Nov 2018 at 14:36, Aditya Tayade <Aditya.Tayade@kpit.com> wrote:
> > Can any one please help me to understand PACKAGECONFIG_remove feature
> >
> >
> > Let's take an example of systemd recipe as follows:
> >
> > PACKAGECONFIG ??= "vconsole"
> >
> > PACKAGECONFIG[vconsole] = "-Dvconsole=true,-Dvconsole=false,,${PN}-vconsole-setup"
> >
> >
> > Now how should we disable features set in PACKAGECONFIG[vconsole] using PACKAGECONFIG_remove from it's bbappend file?
>
> The _remove override removes a value from a variable. So this will
> remove 'vconsole' from the value of PACKAGECONFIG:
>
> PACKAGECONFIG_remove = "vconsole"
>

I also wondered quite a while in the past why such questions are not covered
by the Mega Manual.

https://www.yoctoproject.org/docs/2.5.1/mega-manual/mega-manual.html

Once I had been told that the mega manual contains "everything". As matter of
fact that is not true. Basic syntax for bitbake (recipes and conf files) is
documented only in a separate Bitbake User Manual.

https://www.yoctoproject.org/docs/2.5.1/bitbake-user-manual/bitbake-user-manual.html#removing-override-style-syntax

Regards,

Uwe Geuder
Neuro Event Labs Oy
Tampere, Finland
uwe.gexder@neuroeventlabs.com (Bot check: fix one obvious typo)


  reply	other threads:[~2018-11-09 15:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-09 14:18 so how does PACKAGECONFIG_remove really work? Aditya Tayade
2018-11-09 14:21 ` Aditya Tayade
2018-11-09 14:40   ` Burton, Ross
2018-11-09 15:01     ` Uwe Geuder [this message]
2018-11-09 15:05     ` Aditya Tayade

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=87wopmz449.fsf@snkmail.com \
    --to=jrswdnan22@snkmail.com \
    --cc=yocto@yoctoproject.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.