From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: atharvanandanwar@outlook.com, openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [master][PATCH] meta-toolchain: inherit nopackages
Date: Sun, 29 Sep 2024 22:57:49 +0100 [thread overview]
Message-ID: <2bd45ff2788e33784e47a6c3c9d0faab2ca05380.camel@linuxfoundation.org> (raw)
In-Reply-To: <SA1P223MB1187C93538CD6219C8C10402CB752@SA1P223MB1187.NAMP223.PROD.OUTLOOK.COM>
On Sun, 2024-09-29 at 13:55 -0500, Atharva Nandanwar via
lists.openembedded.org wrote:
> From: Atharva Nandanwar <atharvanandanwar@outlook.com>
>
> - buildhistory emits hard error when no files are present in
> package-split.
> - meta-toolchain doesn't install/package any files, hence inheriting
> nopackages should allow building this recipe again
>
> Signed-off-by: Atharva Nandanwar <atharvanandanwar@outlook.com>
> ---
> meta/recipes-core/meta/meta-toolchain.bb | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/recipes-core/meta/meta-toolchain.bb b/meta/recipes-
> core/meta/meta-toolchain.bb
> index 260e03934e..c97cc68ad4 100644
> --- a/meta/recipes-core/meta/meta-toolchain.bb
> +++ b/meta/recipes-core/meta/meta-toolchain.bb
> @@ -2,4 +2,4 @@ SUMMARY = "Meta package for building a installable
> toolchain"
> LICENSE = "MIT"
>
>
> -inherit populate_sdk
> +inherit nopackages populate_sdk
This shouldn't be needed on master since:
meta/classes-recipe/populate_sdk_base.bbclass
has:
inherit image-postinst-intercepts image-artifact-names nopackages
Cheers,
Richard
next prev parent reply other threads:[~2024-09-29 21:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-29 18:55 [master][PATCH] meta-toolchain: inherit nopackages Atharva Nandanwar
2024-09-29 21:57 ` Richard Purdie [this message]
2024-09-29 22:46 ` [OE-core] " Atharva Nandanwar
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=2bd45ff2788e33784e47a6c3c9d0faab2ca05380.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=atharvanandanwar@outlook.com \
--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 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.