On 11-07-11 10:49 PM, Darren Hart wrote:
With the bitbake commit:
7a2a24de094ce8f2e2068bbee6709dfc2cdc69b9
missing base recipe files for bbappends became an error. Rather than creating a
separate kernel development layer for every layer containing a new kernel recipe
name, conditionally set BB_DA
Hi Richard,
Recently I am doing some work related with multilib.
In current code logic, I see packages that defined in "PACKAGES" variable will
be automatically tagged with libxx-PN.
However there seems no logic to handle the PACKAGES_DYNAMIC case. Is it missed?
Besides, there is runtime packa
With the bitbake commit:
7a2a24de094ce8f2e2068bbee6709dfc2cdc69b9
missing base recipe files for bbappends became an error. Rather than creating a
separate kernel development layer for every layer containing a new kernel recipe
name, conditionally set BB_DANGLINGAPPENDS_WARNONLY.
Signed-off-by: Dar
From: Jingdong Lu
Some kernel options were redefined by routerstationpro.cfg and
it will cause some bugs. So remove some configurations which have
been defined in base.cfg or standard.cfg from routerstationpro.cfg.
1) Gerneral setup:
remove CONFIG_EXPERIMENTAL, CONFIG_SYSVIPC, CONFIG_POSI
From: Jingdong Lu
Some kernel options were redefined by routerstationpro.cfg and
it will cause some bugs. So remove some configurations which have
been defined in base.cfg or standard.cfg from routerstationpro.cfg.
Fix bug [YOCTO #1161]
Fix bug [YOCTO #773]
Jingdong Lu (1):
meta/routerstation
On 07/11/2011 09:56 AM, Tom Zanussi wrote:
> On Mon, 2011-07-11 at 09:49 -0700, Darren Hart wrote:
>> That is quite the assortment of config bits - are all of these necessary
>> to explicitly support the eg20t? I'd like to see minimal config
>> fragments both for simplicity as well as avoiding un
On Mon, 2011-07-11 at 09:53 -0700, Darren Hart wrote:
>
> On 07/10/2011 09:26 AM, tom.zanu...@intel.com wrote:
> > From: Tom Zanussi
> >
> > Inital BSP infrastructure for Intel Fish River Island II.
> >
> > Signed-off-by: Tom Zanussi
> > ---
> > meta/cfg/kernel-cache/bsp/fri2/fri2-standard.sc
Hello list,
Is there a interactive menu-based configuration for yocto/poky builds similar
to that provided in Buildroot? Or is someone working on this?
Thanks
Randy
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/y
On Mon, 2011-07-11 at 09:49 -0700, Darren Hart wrote:
> That is quite the assortment of config bits - are all of these necessary
> to explicitly support the eg20t? I'd like to see minimal config
> fragments both for simplicity as well as avoiding unnecessary kernel
> tool warnings about redefinitio
On 07/10/2011 09:26 AM, tom.zanu...@intel.com wrote:
> From: Tom Zanussi
>
> Inital BSP infrastructure for Intel Fish River Island II.
>
> Signed-off-by: Tom Zanussi
> ---
> meta/cfg/kernel-cache/bsp/fri2/fri2-standard.scc |7 ++
> meta/cfg/kernel-cache/bsp/fri2/fri2.cfg | 69
That is quite the assortment of config bits - are all of these necessary
to explicitly support the eg20t? I'd like to see minimal config
fragments both for simplicity as well as avoiding unnecessary kernel
tool warnings about redefinitions.
--
Darren
On 07/10/2011 09:26 AM, tom.zanu...@intel.com
On 07/06/2011 10:26 PM, G Rajender wrote:
> Hi Darren,
>
> Thank you very much for your reply.
> now i am confident that meta-beagleboard BSP images will work on
> Beagleboard-xM rev B.
> Can you please suggest the steps to follow on how to build from the git
> repository and execute on Beagle
Op 6 jul 2011, om 18:42 heeft Darren Hart het volgende geschreven:
>
>
> On 07/06/2011 07:00 AM, G Rajender wrote:
>> Hi,
>>
>>
>>
>> I am new to Yocto project and Beagleboard.
>>
>>
>>
>> I am using Beagleboard-xM rev B. I got the information about Yocto
>> project by search. Yocto is a
From: Liping Ke
This patch is to cache target dependency tree for Hob (cache impl).
Hob User might switch between different configuration combinations
(machine, sdk-machine, distro, etc). Each dependency re-calcuation
might be time consuming. We use a hashset to cache those result for
avoiding re
From: Liping Ke
This patch is the centralized place for storing Hob attributes.
Most of informations in Prefs will be used when caching user-select
packages information. Those information will be the cache hash-key
which is useful in deciding whether the configuration combination
value has been c
From: Liping Ke
The two patches are the implmentation of Hob Cache for accelarating
UI switching. If one configuration has been saved before, when user
switch back to the same configuration combination, we will use the
cache content instead of re-triggering parsing/loading phase.
The following c
16 matches
Mail list logo
