All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Volk <f_l_k@t-online.de>
To: raj.khem@gmail.com
Cc: f_l_k@t-online.de,
	"Khem Raj via lists.openembedded.org"
	<raj.khem=gmail.com@lists.openembedded.org>,
	openembedded-devel@lists.openembedded.org
Subject: Re: [oe] [meta-multimedia][PATCH] libheif: add recipe
Date: Mon, 06 Jan 2025 17:29:58 +0100	[thread overview]
Message-ID: <YTDOPS.20WRIKFYPCWR@t-online.de> (raw)
In-Reply-To: <CAMKF1so=cPOWjf7GOHL2LhR0OD_3dC5Yute1gL5nWt9gyJ=C3Q@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 763 bytes --]

On Mon, Jan 6 2025 at 07:24:30 -08:00:00, Khem Raj via 
lists.openembedded.org <raj.khem=gmail.com@lists.openembedded.org> 
wrote:
> it fails layer compat check see


x265 is restricted to x86 systems.
I would recommend to drop the restriction. For example it also builds 
for qemuarm


In addition the libheif.bb lacks an entry for LICENSE_FLAGS_ACCEPTED = 
"commercial"


openh264 and libde265 are not added as RDEPENDS in:
 
<https://github.com/openembedded/meta-openembedded/blob/master/meta-multimedia/recipes-multimedia/packagegroups/packagegroup-meta-multimedia.bb>

Is there a reason, why they are not added as RDEPENDS by default? If so 
I'll move the libheif recipe to my personal layer
If it's ok to add them, I'll send a v2 trying to fix the issues



[-- Attachment #2: Type: text/html, Size: 1265 bytes --]

  reply	other threads:[~2025-01-06 16:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-05 18:16 [meta-multimedia][PATCH] libheif: add recipe Markus Volk
2025-01-06 15:24 ` [oe] " Khem Raj
2025-01-06 16:29   ` Markus Volk [this message]
2025-01-06 18:23     ` 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=YTDOPS.20WRIKFYPCWR@t-online.de \
    --to=f_l_k@t-online.de \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=raj.khem=gmail.com@lists.openembedded.org \
    --cc=raj.khem@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.