public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Anton Mikanovich <amikan@ilbers.de>
To: chris.larson@siemens.com, isar-users@googlegroups.com
Cc: Cedric Hombourger <cedric.hombourger@siemens.com>,
	Uladzimir Bely <ubely@ilbers.de>
Subject: Re: [PATCH] features_check: add bbclass from oe-core 1a2afcd0
Date: Tue, 29 Apr 2025 12:42:35 +0300	[thread overview]
Message-ID: <a7f93186-5798-4ca7-915f-2013b908391a@ilbers.de> (raw)
In-Reply-To: <20250328202532.15607-1-chris.larson@siemens.com>

28/03/2025 22:25, chris.larson via isar-users wrote:
> From: Christopher Larson <chris.larson@siemens.com>
>
> Allow checking of required and conflicting features.
>
>      xxx = [DISTRO,MACHINE,COMBINED,IMAGE,BSP,ROOTFS]
>
>      ANY_OF_xxx_FEATURES:        ensure at least one item on this list is included
>                                  in xxx_FEATURES.
>      REQUIRED_xxx_FEATURES:      ensure every item on this list is included
>                                  in xxx_FEATURES.
>      CONFLICT_xxx_FEATURES:      ensure no item in this list is included in
>                                  xxx_FEATURES.
>
> This allows one to easily specify that a given feature is required for a
> recipe. By using this with the new features variables, we can ensure
> that features are set correctly for a given recipe.
>
> We can use simple checks like this:
>
>      REQUIRED_BSP_FEATURES += "some-bsp-feature"
>
> In combination with inline python, we can implement behaviors and checks
> like this:
>
>      # Enable the 'wayland' image feature if the machine feature is enabled.
>      IMAGE_FEATURES:append = " ${@bb.utils.filter('MACHINE_FEATURES', 'wayland', d)}"
>
>      # Require the 'wayland' machine feature when the image feature is enabled.
>      REQUIRED_MACHINE_FEATURES += "${@bb.utils.filter('IMAGE_FEATURES', 'wayland', d)}"
>
> Signed-off-by: Christopher Larson <chris.larson@siemens.com>

Applied to next, thanks.

-- 
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/a7f93186-5798-4ca7-915f-2013b908391a%40ilbers.de.

      reply	other threads:[~2025-04-29  9:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-28 20:25 chris.larson via isar-users
2025-04-29  9:42 ` Anton Mikanovich [this message]

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=a7f93186-5798-4ca7-915f-2013b908391a@ilbers.de \
    --to=amikan@ilbers.de \
    --cc=cedric.hombourger@siemens.com \
    --cc=chris.larson@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=ubely@ilbers.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox