From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Koen Kooi <koen@dominion.thruhere.net>
Subject: Re: [PATCH v2] bluez4: split gstreamer plugin into a seperate recipe
Date: Mon, 26 Sep 2011 16:19:42 -0700 [thread overview]
Message-ID: <4E81088E.8080606@linux.intel.com> (raw)
In-Reply-To: <1316673733-24576-1-git-send-email-koen@dominion.thruhere.net>
On 09/21/2011 11:42 PM, Koen Kooi wrote:
> This eliminates a good chunk of buildtime when building console-only image.
>
> The bluez4 and this recipe share a .inc file since the source is the same.
>
> Signed-off-by: Koen Kooi<koen@dominion.thruhere.net>
> ---
> meta/recipes-connectivity/bluez/bluez4.inc | 37 +++++++++++++++
> meta/recipes-connectivity/bluez/bluez4_4.96.bb | 49 +++-----------------
> .../bluez/gst-plugin-bluetooth_4.96.bb | 28 +++++++++++
> 3 files changed, 72 insertions(+), 42 deletions(-)
> create mode 100644 meta/recipes-connectivity/bluez/bluez4.inc
> create mode 100644 meta/recipes-connectivity/bluez/gst-plugin-bluetooth_4.96.bb
>
Merged into OE-Core
Thanks
Sau!
prev parent reply other threads:[~2011-09-26 23:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-22 6:42 [PATCH v2] bluez4: split gstreamer plugin into a seperate recipe Koen Kooi
2011-09-26 23:19 ` Saul Wold [this message]
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=4E81088E.8080606@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=koen@dominion.thruhere.net \
--cc=openembedded-core@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