From: "Anuj Mittal" <anuj.mittal@intel.com>
To: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>,
"jpewhacker@gmail.com" <jpewhacker@gmail.com>
Subject: Re: [OE-core][PATCH] libomxil: Fix up commercial license flag
Date: Tue, 16 Feb 2021 03:57:00 +0000 [thread overview]
Message-ID: <8fc2f4ea2c7f876557519b5717e30560b6137c79.camel@intel.com> (raw)
In-Reply-To: <7a213c0e-3abe-d100-e38e-3d4ef77a5f6c@gmail.com>
Yes, I have picked this and the weston change.
Thanks,
Anuj
On Mon, 2021-02-15 at 10:47 -0600, Joshua Watt wrote:
> Can this please be backported to gatesgarth?
>
> On 2/12/21 10:51 AM, Joshua Watt wrote:
> > The commercial license flag on libomxil is set because it may
> > include
> > the Adaptive Multi-Rate audio codec (AMR) using FFmepg, which is
> > patent
> > encumbered.
> >
> > It turns out this component is disabled by default in the recipe;
> > add a
> > PACKAGECONFIG to enable it and trigger the "commercial"
> > LICENSE_FLAGS on
> > it. This make the default build configuration clean unless a user
> > specifically asks for AMR support, and prevents them from marking
> > the
> > recipe with the "commerical" flag unnecessarily which could hide
> > potential problems later on.
> >
> > Signed-off-by: Joshua Watt <JPEWhacker@gmail.com>
> > ---
> > meta/recipes-multimedia/libomxil/libomxil_0.9.3.bb | 6 +++++-
> > 1 file changed, 5 insertions(+), 1 deletion(-)
> >
> > diff --git a/meta/recipes-multimedia/libomxil/libomxil_0.9.3.bb
> > b/meta/recipes-multimedia/libomxil/libomxil_0.9.3.bb
> > index 2061c280e4..82cdaf54c7 100644
> > --- a/meta/recipes-multimedia/libomxil/libomxil_0.9.3.bb
> > +++ b/meta/recipes-multimedia/libomxil/libomxil_0.9.3.bb
> > @@ -4,7 +4,7 @@ DESCRIPTION = "Bellagio is an opensource
> > implementation of the Khronos OpenMAX \
> > HOMEPAGE = "http://omxil.sourceforge.net/"
> >
> > LICENSE = "LGPLv2.1+"
> > -LICENSE_FLAGS = "commercial"
> > +LICENSE_FLAGS = "${@bb.utils.contains('PACKAGECONFIG', 'amr',
> > 'commercial', '', d)}"
> > LIC_FILES_CHKSUM =
> > "file://COPYING;md5=ae6f0f4dbc7ac193b50f323a6ae191cb \
> >
> > file://src/omxcore.h;beginline=1;endline=27;md5=806b1e5566c06486fe8e42b461e03a90
> > "
> >
> > @@ -28,6 +28,10 @@ PROVIDES += "virtual/libomxil"
> >
> > CFLAGS += "-fcommon"
> >
> > +PACKAGECONFIG ??= ""
> > +
> > +PACKAGECONFIG[amr] = "--enable-amr,,"
> > +
> > #
> > # The .so files under ${libdir}/bellagio are not intended to be
> > versioned and symlinked.
> > # Make sure they get packaged in the main package.
prev parent reply other threads:[~2021-02-16 3:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-12 16:51 [OE-core][PATCH] libomxil: Fix up commercial license flag Joshua Watt
2021-02-15 16:47 ` Joshua Watt
2021-02-16 3:57 ` Anuj Mittal [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=8fc2f4ea2c7f876557519b5717e30560b6137c79.camel@intel.com \
--to=anuj.mittal@intel.com \
--cc=jpewhacker@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox