On 07/18/10 22:25, Richard Purdie wrote:
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 <d...@vollmann.ch> wrote:

On 07/18/10 17:13, Chris Larson wrote:

On Sun, Jul 18, 2010 at 3:06 AM, Detlef Vollmann <d...@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...
Thanks, that actually works. Great :-)

Thanks again,
  Detlef


_______________________________________________
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

Reply via email to