Poky Project Discussions
 help / color / mirror / Atom feed
From: Matt Madison <madison@cisco.com>
To: Joshua Lock <josh@linux.intel.com>, Poky Mailer <poky@yoctoproject.org>
Subject: Re: Distro policy ?
Date: Thu, 14 Apr 2011 16:00:35 -0700	[thread overview]
Message-ID: <C9CCCAA3.415A9%madison@cisco.com> (raw)
In-Reply-To: <1302817417.8711.2.camel@scimitar>

How about when it's the other way round -- you need to modify just the .inc
for your layer, and not the recipes that require/include them?  Should all
recipes in the core be changed to use the path name syntax to enable that?

Thanks,
-Matt


On 4/14/11 14:43 , "Joshua Lock" <josh@linux.intel.com> wrote:

> On Thu, 2011-04-14 at 21:44 +0200, Wolfgang Denk wrote:
>> HI,
>> 
>> we're trying to build our own distribution based on Yocto 1.0.  We
>> would like to push all modifications / extensions and our distro stuff
>> upstream into the mainline repository, but we are not sure what is the
>> best way to do this:
>> 
>> So far we have put our distro-related changes into a separate layer
>> but it seems that it was not so good idea: it looks like bitbake
>> can't include files from one layer to another and we have to copy
>> includes even if we don't want to change them.
> 
> You can you just have to use a path from the top of the BBPATH entry for
> the layer you're using, so in our meta-demo layer I've used entries
> like:
> 
> require recipes-graphics/clutter/clutter.inc
> 
> to use an inc file from meta in Poky.
> 
> Cheers,
> Joshua



  reply	other threads:[~2011-04-14 23:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-14 19:44 Distro policy ? Wolfgang Denk
2011-04-14 20:28 ` Saul Wold
2011-04-14 20:57   ` Chris Larson
2011-04-14 21:12     ` Martin Jansa
2011-04-14 21:19       ` Chris Larson
2011-04-20 22:39         ` Ilya Yanok
2011-04-20 22:56   ` Ilya Yanok
2011-04-14 21:43 ` Joshua Lock
2011-04-14 23:00   ` Matt Madison [this message]
2011-04-15 15:34     ` Richard Purdie
2011-04-20 22:44   ` Ilya Yanok

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=C9CCCAA3.415A9%madison@cisco.com \
    --to=madison@cisco.com \
    --cc=josh@linux.intel.com \
    --cc=poky@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox