From: Scott Garman <scott.a.garman@intel.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: McClintock Matthew-B29882 <B29882@freescale.com>,
"yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: best cfg for building all of yocto?
Date: Thu, 21 Jul 2011 10:39:05 -0700 [thread overview]
Message-ID: <4E286439.6000601@intel.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1107211307240.4686@localhost6.localdomain6>
On 07/21/2011 10:08 AM, Robert P. J. Day wrote:
> On Thu, 21 Jul 2011, Scott Garman wrote:
>
>> On 07/21/2011 09:32 AM, McClintock Matthew-B29882 wrote:
>>> On Thu, Jul 21, 2011 at 8:29 AM, Scott Garman<scott.a.garman@intel.com>
>>> wrote:
>>>> bitbake world should build all of the available packages that aren't
>>>> explicitly excluded due to machine incompatibilities. It doesn't generate
>>>> a
>>>> final image though, just all of the output packages.
>>>
>>> Is there an easy way to remove a specific package from being built
>>> with running bitbake world? There are unmet dependencies:
>>>
>>> NOTE: Resolving any missing task queue dependencies
>>> ERROR: Nothing PROVIDES 'libmad'
>>> ERROR: Required build target 'libomxil' has no buildable providers.
>>> Missing or unbuildable dependency chain was: ['libomxil', 'libmad']
>>
>> This happens because conf/distro/include/default-distrovars.inc excludes some
>> recipes which are known to use commercial licenses:
>>
>> COMMERCIAL_LICENSE ?= "lame gst-fluendo-mp3 libmad mpeg2dec ffmpeg qmmp"
>>
>> If you'd like to build these recipes, set COMMERCIAL_LICENSE = "" in your
>> local.conf.
>
> related to richard's earlier post about how to exclude packages,
> shouldn't the initial settings be consistent, then? either a default
> yocto setup should include commercial licenses, or exclude them (and
> their packages) entirely. it seems that running a simple "bitbake
> world" shouldn't just fail.
I agree with Robert. I have filed bug #1262 to track this issue.
Scott
--
Scott Garman
Embedded Linux Engineer - Yocto Project
Intel Open Source Technology Center
next prev parent reply other threads:[~2011-07-21 17:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-21 5:10 best cfg for building all of yocto? Kumar Gala
2011-07-21 13:29 ` Scott Garman
2011-07-21 16:32 ` McClintock Matthew-B29882
2011-07-21 16:36 ` Robert P. J. Day
2011-07-21 16:37 ` Richard Purdie
2011-07-21 16:43 ` Scott Garman
2011-07-21 17:08 ` Robert P. J. Day
2011-07-21 17:39 ` Scott Garman [this message]
2011-07-21 21:23 ` Koen Kooi
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=4E286439.6000601@intel.com \
--to=scott.a.garman@intel.com \
--cc=B29882@freescale.com \
--cc=rpjday@crashcourse.ca \
--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.