All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: best practice .inc files
Date: Wed, 20 Jul 2011 10:26:46 +0100	[thread overview]
Message-ID: <201107201026.46169.paul.eggleton@linux.intel.com> (raw)
In-Reply-To: <4E269D1F.9070009@nedap.com>

On Wednesday 20 July 2011 10:17:19 Jaap de Jong wrote:
> I'm using the 2010.12 release.
> I've created my own u-boot_2010.09.bb file in my local repository.
> In it is aline
>      require u-boot.inc
> (every u-boot*.bb recipe has it)
> Now I need a copy of the openembedded/recipes/u-boot/u-boot.inc in my
> local repository to get it bitbaked.
> (Well actually I've symlinked the file)
> I think both solutions are not optimal.
> Is there a way to this in a more gentle way?

If you use the path starting from the base i.e. "require recipes/u-boot/u-
boot.inc" it should work.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre



      reply	other threads:[~2011-07-20  9:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-20  9:17 best practice .inc files Jaap de Jong
2011-07-20  9:26 ` Paul Eggleton [this message]

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=201107201026.46169.paul.eggleton@linux.intel.com \
    --to=paul.eggleton@linux.intel.com \
    --cc=openembedded-devel@lists.openembedded.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.