From: Petter Mabacker <petter@technux.se>
To: Khem Raj <raj.khem@gmail.com>
Cc: yocto <yocto@yoctoproject.org>, mohammed aqdam <mohammedaqdam@gmail.com>
Subject: Re: Errors while tring rpi-test-image for rpi3
Date: Tue, 15 Aug 2017 08:29:24 +0200 [thread overview]
Message-ID: <1502778564.7630.25.camel@technux.se> (raw)
In-Reply-To: <CAMKF1spVyE42CTQvbk0gzHoyUtqAYRyGdcAO3GcwLjts2T=0-Q@mail.gmail.com>
On Sun, 2017-08-13 at 09:28 -0700, Khem Raj wrote:
> On Sat, Aug 12, 2017 at 11:42 PM, Petter Mabacker <petter@technux.se>
> wrote:
> > On Sat, 2017-08-12 at 15:10 +0300, Jussi Kukkonen wrote:
> >
> > > ERROR: Nothing PROVIDES 'libav' (but
> > >
> > > /u/hope_poky/poky_for_mon/poky/meta-raspberrypi/recipes-
> > > multimedia/omxplayer/omxplayer_git.bb
> > > DEPENDS on or otherwise requires it)
> > > ERROR: ffmpeg PROVIDES libav but was skipped: because it has a
> > > restricted license not whitelisted in LICENSE_FLAGS_WHITELIST
> >
> > Searching the Yocto reference manual for this term will lead to
> > http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html
> > #enabling-commercially-licensed-recipes
> > which should have the details you need to resolve the issue.
> >
> > Jussi
> >
> >
> > Hi,
> >
> > This info is actually also present in the meta-raspberrypi
> > documentation, in
> > 'docs/extra-apps.md':
> >
> > $ cat docs/extra-apps.md
> > # Extra apps
> >
> > ## omxplayer
> >
> > omxplayer depends on libav which has a commercial license. So in
> > order to be
> > able to compile omxplayer you will need to whiteflag the commercial
> > license in your local.conf:
> >
> > LICENSE_FLAGS_WHITELIST = "commercial"
> >
>
> it is better to be cautious about it and enable what you want and
> ensure you can do so from licesning perspective.
>
> LICENSE_FLAGS_WHITELIST_append = " commercial_libomxil "
>
> e.g. will enable only for libomxil and keep adding to this list the
> licenses you want to white list.
>
I agree, it sounds resonable. We should probably update the above
mentioned doc (docs/extra-apps.md) with this info..
BR Petter
> >
> >
> > To make full use of the documentation I recommend that you are
> > generating
> > the documentation within docs/ in for example html format and make
> > use of
> > the searching functionality in there.
> >
> >
> > BR Petter
> >
> > --
> > _______________________________________________
> > yocto mailing list
> > yocto@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/yocto
> >
prev parent reply other threads:[~2017-08-15 6:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-12 8:08 Errors while tring rpi-test-image for rpi3 mohammed aqdam
2017-08-12 8:33 ` Jussi Kukkonen
2017-08-12 10:40 ` mohammed aqdam
2017-08-12 12:10 ` Jussi Kukkonen
2017-08-13 6:42 ` Petter Mabacker
2017-08-13 16:28 ` Khem Raj
2017-08-15 6:29 ` Petter Mabacker [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=1502778564.7630.25.camel@technux.se \
--to=petter@technux.se \
--cc=mohammedaqdam@gmail.com \
--cc=raj.khem@gmail.com \
--cc=yocto@yoctoproject.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.