From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Cc: koen@dominion.thruhere.net
Subject: Re: [PATCH 3/3] bluez4: Add 4.91 and make it default for Angstrom
Date: Mon, 25 Apr 2011 20:43:31 +0200 [thread overview]
Message-ID: <20110425184331.GA3376@jama.jama.net> (raw)
In-Reply-To: <1303756273-22385-4-git-send-email-tom_rini@mentor.com>
[-- Attachment #1: Type: text/plain, Size: 1435 bytes --]
On Mon, Apr 25, 2011 at 11:31:13AM -0700, Tom Rini wrote:
> Signed-off-by: Tom Rini <tom_rini@mentor.com>
> ---
> recipes/bluez/bluez4_4.91.bb | 18 ++++++++++++++++++
> 1 files changed, 18 insertions(+), 0 deletions(-)
> create mode 100644 recipes/bluez/bluez4_4.91.bb
>
> diff --git a/recipes/bluez/bluez4_4.91.bb b/recipes/bluez/bluez4_4.91.bb
> new file mode 100644
> index 0000000..16f06d5
> --- /dev/null
> +++ b/recipes/bluez/bluez4_4.91.bb
> @@ -0,0 +1,18 @@
> +require bluez4.inc
> +
> +SRC_URI[md5sum] = "3059b7ef5168c84cd0c6a67034ce79f9"
> +SRC_URI[sha256sum] = "11e9279e2669db996afd464b96d2c68f41f157f6eb9b8842a0bbcad8a4eac18d"
> +
> +DEFAULT_PREFERENCE = "-1"
> +DEFAULT_PREFERENCE_angstrom = "1"
please make it default for shr too, we're using bluez4_4.91 now from
meta-oe and it works ok, so we can keep it in sync, thanks
> +
> +DEPENDS += "libsndfile1"
> +
> +PR = "${INC_PR}.0"
> +
> +# Not all distros have a recent enough udev
> +BTUDEV = " --disable-udevrules"
> +BTUDEV_angstrom = " --enable-udevrules"
> +BTUDEV_shr = " --enable-udevrules"
> +
> +EXTRA_OECONF += "${BTUDEV}"
> --
> 1.7.0.4
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2011-04-25 18:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-25 18:31 [RFC, PATCH] Add minver/maxver to patch.bbclass, update bluez Tom Rini
2011-04-25 18:31 ` [PATCH 1/3] patch.bbclass: Add minver/maxver params Tom Rini
2011-04-25 18:31 ` [PATCH 2/3] bluez4.inc: List 4.90 as the maxver for applying a patch Tom Rini
2011-04-25 18:31 ` [PATCH 3/3] bluez4: Add 4.91 and make it default for Angstrom Tom Rini
2011-04-25 18:33 ` Koen Kooi
2011-04-25 18:43 ` Martin Jansa [this message]
2011-04-25 18:54 ` Paul Menzel
2011-04-25 19:05 ` Tom Rini
2011-04-25 19:18 ` Eric Bénard
2011-04-25 20:14 ` [RFC, PATCH] Add minver/maxver to patch.bbclass, update bluez Frans Meulenbroeks
2011-04-25 20:40 ` Tom Rini
2011-04-25 20:52 ` Frans Meulenbroeks
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=20110425184331.GA3376@jama.jama.net \
--to=martin.jansa@gmail.com \
--cc=koen@dominion.thruhere.net \
--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.