best cfg for building all of yocto?

best cfg for building all of yocto?

[Kumar Gala]

For a new bsp/target what's the best config choice to try and build all of yocto?  Is it core-image-sato?

- k

Re: best cfg for building all of yocto?

[Scott Garman]

On 07/20/2011 10:10 PM, Kumar Gala wrote:
> For a new bsp/target what's the best config choice to try and build all of yocto?  Is it core-image-sato?
>
> - k

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.

core-image-lsb builds a significantly larger set of packages than -sato 
if you want a reference image that includes more packages.

Scott

-- 
Scott Garman
Embedded Linux Engineer - Yocto Project
Intel Open Source Technology Center

Re: best cfg for building all of yocto?

[McClintock Matthew-B29882]

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']

-M

Re: best cfg for building all of yocto?

[Robert P. J. Day]

On Thu, 21 Jul 2011, 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']

  i saw that a couple days ago but i figured someone else would pick
up on it in short order.

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

Re: best cfg for building all of yocto?

[Richard Purdie]

On Thu, 2011-07-21 at 16:32 +0000, 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']

EXCLUDE_FROM_WORLD_pn-libmad = "1"

should remove libmad from world builds.

Cheers,

Richard

Re: best cfg for building all of yocto?

[Scott Garman]

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.

Scott

-- 
Scott Garman
Embedded Linux Engineer - Yocto Project
Intel Open Source Technology Center

Re: best cfg for building all of yocto?

[Robert P. J. Day]

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.

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

Re: best cfg for building all of yocto?

[Scott Garman]

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

Re: best cfg for building all of yocto?

[Koen Kooi]

Op 21 jul. 2011, om 18:43 heeft Scott Garman het volgende geschreven:

> 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"


COMMERCIAL_LICENSE is a mis-nomber for a lot of them, NEED_TO_GIVE_MONEY_TO_MPEGLA is closer to the truth. What I'm trying to say is that the recipes in question don't have a commercial license, but can be subject to royalties in some cases. It could be that  your silicon vendor already pays the royalty for you for each chip they sell, so it is helpfull to dig into this before tweaking COMMERCIAL_LICENSE.