From: Michael Smith <msmith@cbnco.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: A new bitbake extension: .bbappend files
Date: Tue, 20 Jul 2010 11:52:30 -0400 [thread overview]
Message-ID: <4C45C63E.70306@cbnco.com> (raw)
In-Reply-To: <4C45BE9F.7000002@mentor.com>
Tom Rini wrote:
> It's also needed, in some cases, to lock down your changes via OVERRIDES
> that will only match what you want to work on. For example, we're using
> a snapshot with an older python, so amend.inc in our python directory
> looks like:
>
> SRC_URI_append_pn-python-native =
> "file://python-2.6-r73342.patch;patch=1;pnum=0"
> PARALLEL_MAKE_pn-python-native = ""
> PR_append_pn-python-native .= ".1"
>
> So that we only change python-native and not all of the other python
> recipes.
I think you could get the same effect by putting your amend.inc in a
python-native subdirectory under your overlay recipes/python directory.
Maybe there's some native magic going on that would break that. (I've
never amended a -native package but I use the same trick for other
recipes where there are multiple .bb files are in the same OE directory.)
Mike
next prev parent reply other threads:[~2010-07-20 15:52 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
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 [this message]
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=4C45C63E.70306@cbnco.com \
--to=msmith@cbnco.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.