BSPs and duplicate files


João Henrique Ferreira de Freitas
 

Hi,

Two questions:

With some BSPs, like

meta
meta-myhardware
meta-mydistro

I need to create a conf/checksums.ini for every BSP or append it to
meta/conf/checksums.ini ? In other others, checksums.ini is per BSP or
unique?

In my meta-myhardware I have a kernel too:

meta-myhardware/recipes-kernel/linux/linux.inc
meta-myhardware/recipes-kernel/linux/linux_2.6.22.bb

The file meta-myhardware/recipes-kernel/linux/linux.inc is the some of
meta/recipes-kernel/linux/linux.inc. Is any way to use a unique file
instead of duplicate it?

--
-----------------------------------------------------------
João Henrique Freitas - joaohf_at_gmail.com
Campinas-SP-Brasil
BSD051283
LPI 1
http://www.joaohfreitas.eti.br


Joshua Lock <josh@...>
 

On Thu, 2010-11-11 at 13:19 -0200, João Henrique Freitas wrote:
Hi,

Two questions:

With some BSPs, like

meta
meta-myhardware
meta-mydistro

I need to create a conf/checksums.ini for every BSP or append it to
meta/conf/checksums.ini ? In other others, checksums.ini is per BSP or
unique?
I'm not sure about this one, hopefully someone else can help you here.


In my meta-myhardware I have a kernel too:

meta-myhardware/recipes-kernel/linux/linux.inc
meta-myhardware/recipes-kernel/linux/linux_2.6.22.bb

The file meta-myhardware/recipes-kernel/linux/linux.inc is the some of
meta/recipes-kernel/linux/linux.inc. Is any way to use a unique file
instead of duplicate it?
You can include files from the core metadata by using a path relative to
the meta/ directory, such as:

require recipes-kernel/linux/linux.inc

Cheers,
Joshua
--
Joshua Lock
Intel Open Source Technology Centre


João Henrique Ferreira de Freitas
 

Hi

You can include files from the core metadata by using a path relative to
the meta/ directory, such as:

require recipes-kernel/linux/linux.inc

Works


Thanks
--
-----------------------------------------------------------
João Henrique Freitas - joaohf_at_gmail.com
Campinas-SP-Brasil
BSD051283
LPI 1
http://www.joaohfreitas.eti.br


Philip Balister
 

On 11/11/2010 07:19 AM, João Henrique Freitas wrote:
Hi,

Two questions:

With some BSPs, like

meta
meta-myhardware
meta-mydistro

I need to create a conf/checksums.ini for every BSP or append it to
meta/conf/checksums.ini ? In other others, checksums.ini is per BSP or
unique?
Poky still uses checksums.ini? OE moved the checksums to the recipes and this seems make things much easier to work with.

Philip


In my meta-myhardware I have a kernel too:

meta-myhardware/recipes-kernel/linux/linux.inc
meta-myhardware/recipes-kernel/linux/linux_2.6.22.bb

The file meta-myhardware/recipes-kernel/linux/linux.inc is the some of
meta/recipes-kernel/linux/linux.inc. Is any way to use a unique file
instead of duplicate it?


Scott Garman <scott.a.garman@...>
 

On 11/11/2010 04:16 PM, Philip Balister wrote:
On 11/11/2010 07:19 AM, João Henrique Freitas wrote:
Hi,

Two questions:

With some BSPs, like

meta
meta-myhardware
meta-mydistro

I need to create a conf/checksums.ini for every BSP or append it to
meta/conf/checksums.ini ? In other others, checksums.ini is per BSP or
unique?
Poky still uses checksums.ini? OE moved the checksums to the recipes and
this seems make things much easier to work with.
We'll be switching to recipe-based checksums soon in master, and in fact you'll notice that most of our recipes already have checksums in them. It's just a matter of importing the code from OE and making whatever tweaks might be necessary.

Scott

--
Scott Garman
Embedded Linux Distro Engineer - Yocto Project


Philip Balister
 

On 11/11/2010 07:58 PM, Scott Garman wrote:
On 11/11/2010 04:16 PM, Philip Balister wrote:
On 11/11/2010 07:19 AM, João Henrique Freitas wrote:
Hi,

Two questions:

With some BSPs, like

meta
meta-myhardware
meta-mydistro

I need to create a conf/checksums.ini for every BSP or append it to
meta/conf/checksums.ini ? In other others, checksums.ini is per BSP or
unique?
Poky still uses checksums.ini? OE moved the checksums to the recipes and
this seems make things much easier to work with.
We'll be switching to recipe-based checksums soon in master, and in fact
you'll notice that most of our recipes already have checksums in them.
It's just a matter of importing the code from OE and making whatever
tweaks might be necessary.
Good to know. I don't think one approach is technically better than the other, but when you have a "large" community, it seemed like one checksum file lead to merge conflicts.

Philip