All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joshua Lock <josh@linux.intel.com>
To: "João Henrique Freitas" <joaohf@gmail.com>
Cc: yocto@yoctoproject.org
Subject: Re: BSPs and duplicate files
Date: Thu, 11 Nov 2010 15:38:09 +0000	[thread overview]
Message-ID: <1289489889.2453.1.camel@scimitar> (raw)
In-Reply-To: <AANLkTi=7yQCQB4=bKYuW3DTx4-psGZPDKkQeum+qdw3=@mail.gmail.com>

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



  reply	other threads:[~2010-11-11 15:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-11 15:19 BSPs and duplicate files João Henrique Freitas
2010-11-11 15:38 ` Joshua Lock [this message]
2010-11-11 21:39   ` João Henrique Freitas
2010-11-12  0:16 ` Philip Balister
2010-11-12  3:58   ` Scott Garman
2010-11-12 17:42     ` Philip Balister

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=1289489889.2453.1.camel@scimitar \
    --to=josh@linux.intel.com \
    --cc=joaohf@gmail.com \
    --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.