From: Marcin Juszkiewicz <marcin@juszkiewicz.com.pl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: RFC: Improve our default conf file setup
Date: Thu, 18 Feb 2010 10:09:06 +0100 [thread overview]
Message-ID: <201002181009.07359.marcin@juszkiewicz.com.pl> (raw)
In-Reply-To: <1266334604.6436.159.camel@rex>
Dnia wtorek, 16 lutego 2010 o 16:36:44 Richard Purdie napisał(a):
> c) Are recipes in a recipes or a packages directory?
> d) How deep are the paths to the .bb files?
BBFILES += "layer-top-dir" and BitBake will traverse subdirs and collect all
recipes from there. Never mind are they in recipes/ packages/ stuff/ or other
dir. It is working for quite long time now.
> e) What priority are assigned to the layers?
Priorities looks easy when you look at numbers. But problem arrives when you
want layer3 to have higher priority then layer2 and they are not connected.
> f) Should a given layer append or prepend to BBPATH?
Those two are important. I remember situation with BugLabs r1.4 overlays when
I had to recreate BBPATH to get proper order of overlays.
Regards,
--
JID: hrw@jabber.org
Website: http://marcin.juszkiewicz.com.pl/
LinkedIn: http://www.linkedin.com/in/marcinjuszkiewicz
next prev parent reply other threads:[~2010-02-18 9:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-16 10:34 RFC: Improve our default conf file setup Richard Purdie
2010-02-16 10:58 ` Frans Meulenbroeks
2010-02-16 11:00 ` Frans Meulenbroeks
2010-02-16 11:49 ` Richard Purdie
2010-02-16 14:16 ` Chris Larson
2010-02-16 15:36 ` Richard Purdie
2010-02-18 7:47 ` Frans Meulenbroeks
2010-02-18 9:09 ` Marcin Juszkiewicz [this message]
2010-02-18 16:13 ` Chris Larson
2010-02-18 16:58 ` Richard Purdie
2010-02-20 1:39 ` Chris Larson
2010-02-20 22:58 ` Richard Purdie
2010-02-21 1:19 ` Chris Larson
2010-02-23 17:55 ` Richard Purdie
2010-02-23 18:14 ` Chris Larson
2010-02-16 11:15 ` Marco Cavallini
2010-02-16 11:47 ` Richard Purdie
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=201002181009.07359.marcin@juszkiewicz.com.pl \
--to=marcin@juszkiewicz.com.pl \
--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.