On 12/18/2012 11:56 AM, Tom Zanussi wrote:
> On Tue, 2012-12-18 at 11:37 -0500, Philip Balister wrote:
>> On 12/18/2012 09:33 AM, Tom Zanussi wrote:
>>> On Tue, 2012-12-18 at 09:13 -0500, Philip Balister wrote:
On 12/17/2012 12:51 PM, tom.zanu...@intel.com wrote:
> From: Tom Zanussi
>
On Tue, 2012-12-18 at 11:37 -0500, Philip Balister wrote:
> On 12/18/2012 09:33 AM, Tom Zanussi wrote:
> > On Tue, 2012-12-18 at 09:13 -0500, Philip Balister wrote:
> >> On 12/17/2012 12:51 PM, tom.zanu...@intel.com wrote:
> >>> From: Tom Zanussi
> >>>
> >>> Add a new yocto_layer_create() function
On 12/18/2012 09:33 AM, Tom Zanussi wrote:
> On Tue, 2012-12-18 at 09:13 -0500, Philip Balister wrote:
>> On 12/17/2012 12:51 PM, tom.zanu...@intel.com wrote:
>>> From: Tom Zanussi
>>>
>>> Add a new yocto_layer_create() function that will be used to generate
>>> a generic yocto layer (for the new
On Tue, 2012-12-18 at 09:13 -0500, Philip Balister wrote:
> On 12/17/2012 12:51 PM, tom.zanu...@intel.com wrote:
> > From: Tom Zanussi
> >
> > Add a new yocto_layer_create() function that will be used to generate
> > a generic yocto layer (for the new 'yocto-layer' command).
>
> How is a "yocto
On 12/17/2012 12:51 PM, tom.zanu...@intel.com wrote:
> From: Tom Zanussi
>
> Add a new yocto_layer_create() function that will be used to generate
> a generic yocto layer (for the new 'yocto-layer' command).
How is a "yocto layer" different from an OpenEmbedded layer? If you
insist on "yocto lay
From: Tom Zanussi
Add a new yocto_layer_create() function that will be used to generate
a generic yocto layer (for the new 'yocto-layer' command).
Signed-off-by: Tom Zanussi
---
scripts/lib/bsp/engine.py | 56 +++
1 file changed, 56 insertions(+)
di