Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Alejandro Hernandez Samaniego <alejandro@enedino.org>,
	openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] baremetal-image.bbclass: Emulate image.bbclass to handle new classes scope
Date: Tue, 23 Aug 2022 23:13:30 +0100	[thread overview]
Message-ID: <d9d568b0796c77bd44ab82d4dbcc3ae01b0b8972.camel@linuxfoundation.org> (raw)
In-Reply-To: <20220823213124.4185070-1-alejandro@enedino.org>

On Tue, 2022-08-23 at 15:31 -0600, Alejandro Hernandez Samaniego wrote:
> The new classes scope implemented on commit 7bd328f9d
> made testimage.bbclass (and perhaps others) stop working
> for baremetal-images, the expected way to run testimage
> is no longer to use INHERIT but to use IMAGE_CLASSES
> instead, however this functionality was not implemented in the
> baremetal-image class until now.
> 
> Emulate image.bbclass allowing the baremetal-image class to
> use IMAGE_CLASSES to fix this issue.
> 
> Set defaults for IMAGE_FEATURES to allow bitbake checks to
> pass properly.
> 
> Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandro@enedino.org>
> ---
>  meta/classes-recipe/baremetal-image.bbclass | 9 +++++++++
>  1 file changed, 9 insertions(+)
> 
> diff --git a/meta/classes-recipe/baremetal-image.bbclass b/meta/classes-recipe/baremetal-image.bbclass
> index 3a979f2ed1..d3377a92fa 100644
> --- a/meta/classes-recipe/baremetal-image.bbclass
> +++ b/meta/classes-recipe/baremetal-image.bbclass
> @@ -15,6 +15,15 @@
>  #
>  # See meta-skeleton for a working example.
>  
> +## Emulate image.bbclass
> +# Handle inherits of any of the image classes we need
> +IMAGE_CLASSES ??= ""
> +IMGCLASSES = " ${IMAGE_CLASSES}"
> +inherit ${IMGCLASSES}
> +# Set defaults to satisfy IMAGE_FEATURES check
> +IMAGE_FEATURES ?= ""
> +IMAGE_FEATURES[type] = "list"
> +IMAGE_FEATURES[validitems] += ""
>  
>  # Toolchain should be baremetal or newlib based.
>  # TCLIBC="baremetal" or TCLIBC="newlib"


I think we're missing a testcase!

Cheers,

Richard



  reply	other threads:[~2022-08-23 22:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-23 21:31 [PATCH] baremetal-image.bbclass: Emulate image.bbclass to handle new classes scope Alejandro Enedino Hernandez Samaniego
2022-08-23 22:13 ` Richard Purdie [this message]
2022-08-23 23:17   ` [OE-core] " Alejandro Enedino Hernandez Samaniego

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=d9d568b0796c77bd44ab82d4dbcc3ae01b0b8972.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=alejandro@enedino.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox