From: Richard Purdie <rpurdie@rpsys.net>
To: Detlef Vollmann <dv@vollmann.ch>
Cc: bitbake-dev <bitbake-dev@lists.berlios.de>,
openembedded-devel@lists.openembedded.org
Subject: Re: [Bitbake-dev] A new bitbake extension: .bbappend files
Date: Sun, 18 Jul 2010 21:25:16 +0100 [thread overview]
Message-ID: <1279484716.10837.2467.camel@rex> (raw)
In-Reply-To: <4C4354EF.1080004@vollmann.ch>
On Sun, 2010-07-18 at 21:24 +0200, Detlef Vollmann wrote:
> On 07/18/10 18:06, Chris Larson wrote:
> > On Sun, Jul 18, 2010 at 9:01 AM, Detlef Vollmann <dv@vollmann.ch> wrote:
> >
> >> On 07/18/10 17:13, Chris Larson wrote:
> >>
> >>> On Sun, Jul 18, 2010 at 3:06 AM, Detlef Vollmann <dv@vollmann.ch> wrote:
> >>>
> >>> On 07/16/10 16:25, Richard Purdie wrote:
> >>>> For the specific case of paths, I have wondered if there would be a way
> >>>>> to leverage help from bitbake in creating a sane set of search paths but
> >>>>> I'm still thinking about that. This extension is good enough in its own
> >>>>> right in my opinion to be worthwhile.
> >>>>>
> >>>>> This might be true, but solving the general path problem would be
> >>>> much more useful.
> >>>> If you want to add a new version of e.g. gcc in your ovlerlay,
> >>>> you have to pull over the whole gcc directory with all its .inc classes.
> >>>> This can't be solved by .bbapend, or am I missing something?
> >>>>
> >>>
> >>> You can handle that today by adding to FILESPATHBASE. All file:// files
> >>> from SRC_URI are located using FILESPATH, which is constructed from
> >>> FILESPATHBASE, FILESPATHPKG, and OVERRIDES.
> >>>
> >> AFAIK this doen't work for include/require :-(
> >
> >
> > Don't copy the recipe at all, use .bbappend instead, and you won't need to
> > have the .inc in a different collection from the recipe itself.
> In that case I didn't understand .bbappend.
> If I have a recipe gcc_4.3.2.bb in e.g. oe-stable/recipes/gcc, but in
> that directory is no gcc_4.4.4.bb, and I put gcc_4.4.4.bbappend into
> myproject/recipes/gcc, that would probably given an error like
> 'no .bb file to append'.
> At least that's how I understood .bbappend.
>
> > Alternatively, you can adjust BBPATH to also include the other collection
> > based paths + os.path.dirname('${FILE_DIRNAME}') or so.
> I'd be very interested to find a way so that a 'require gcc.inc' in
> myproject/recipes/gcc_4.4.4.bb would find oe-stable/recipes/gcc/gcc.inc.
> So far I failed.
Does something like "require recipes/gcc/gcc.inc" not just work already
as it will search BBPATH...
Cheers,
Richard
next prev parent reply other threads:[~2010-07-18 20:25 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-16 14:25 A new bitbake extension: .bbappend files Richard Purdie
2010-07-16 14:35 ` George C. Huntington, III
2010-07-16 15:37 ` Carl Simonson
2010-07-16 15:46 ` [Bitbake-dev] " Michael Smith
2010-07-16 16:16 ` Chris Larson
2010-07-16 16:24 ` Richard Purdie
2010-07-16 16:53 ` Frans Meulenbroeks
2010-07-18 8:12 ` Esben Haabendal
2010-07-18 10:06 ` Detlef Vollmann
2010-07-18 15:13 ` Chris Larson
2010-07-18 16:01 ` Detlef Vollmann
2010-07-18 16:06 ` Chris Larson
2010-07-18 19:24 ` Detlef Vollmann
2010-07-18 20:25 ` Richard Purdie [this message]
2010-07-18 21:13 ` Detlef Vollmann
2010-07-19 8:31 ` Hauser, Wolfgang (external)
2010-07-18 19:47 ` Frans Meulenbroeks
2010-07-18 20:52 ` Chris Larson
2010-07-18 20:57 ` Frans Meulenbroeks
2010-07-19 0:02 ` Douglas Royds
2010-07-19 20:50 ` Tom Rini
2010-07-19 21:22 ` Chris Larson
2010-07-19 21:24 ` Chris Larson
2010-07-20 7:28 ` Frans Meulenbroeks
2010-07-20 14:06 ` Chris Larson
2010-07-20 15:19 ` Tom Rini
2010-07-20 15:50 ` Tom Rini
2010-07-20 15:52 ` Michael Smith
2010-07-20 16:06 ` Chris Larson
2010-07-20 16:29 ` Frans Meulenbroeks
2010-07-20 16:54 ` Chris Larson
2010-08-03 10:04 ` Frans Meulenbroeks
2010-08-03 12:53 ` Richard Purdie
2010-08-03 19:30 ` Khem Raj
2010-08-03 13:26 ` [Bitbake-dev] " Richard Purdie
2010-08-03 14:13 ` Chris Larson
2010-08-04 4:09 ` Khem Raj
2010-08-04 14:40 ` Richard Purdie
2010-08-04 19:00 ` Khem Raj
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=1279484716.10837.2467.camel@rex \
--to=rpurdie@rpsys.net \
--cc=bitbake-dev@lists.berlios.de \
--cc=dv@vollmann.ch \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox