From: Chih-Min Chao <cmchao@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 4/5] bluez : new package
Date: Mon, 13 Sep 2010 23:12:14 +0800 [thread overview]
Message-ID: <1284390735-2261-5-git-send-email-cmchao@gmail.com> (raw)
In-Reply-To: <1284390735-2261-1-git-send-email-cmchao@gmail.com>
Signed-off-by: Chih-Min Chao <cmchao@gmail.com>
---
package/Config.in | 1 +
package/bluez/Config.in | 11 +++++++++++
package/bluez/bluez.mk | 16 ++++++++++++++++
3 files changed, 28 insertions(+), 0 deletions(-)
create mode 100644 package/bluez/Config.in
create mode 100644 package/bluez/bluez.mk
diff --git a/package/Config.in b/package/Config.in
index 2209b55..e8922c9 100644
--- a/package/Config.in
+++ b/package/Config.in
@@ -353,6 +353,7 @@ if BR2_PACKAGE_BUSYBOX_SHOW_OTHERS
source "package/boa/Config.in"
endif
source "package/bind/Config.in"
+source "package/bluez/Config.in"
source "package/bmon/Config.in"
source "package/bridge-utils/Config.in"
source "package/ctorrent/Config.in"
diff --git a/package/bluez/Config.in b/package/bluez/Config.in
new file mode 100644
index 0000000..d80933e
--- /dev/null
+++ b/package/bluez/Config.in
@@ -0,0 +1,11 @@
+config BR2_PACKAGE_BLUEZ
+ bool "bluez"
+ depends on BR2_PACKAGE_DBUS_GLIB
+ help
+ BlueZ provides support for the core Bluetooth layers and protocols.
+ It is flexible, efficient and uses a modular implementation.
+
+ http://www.bluez.org/
+
+comment "bluez requires dbus-glib2 package
+ depends on !BR2_PACKAGE_DBUS_GLIB
diff --git a/package/bluez/bluez.mk b/package/bluez/bluez.mk
new file mode 100644
index 0000000..39339c5
--- /dev/null
+++ b/package/bluez/bluez.mk
@@ -0,0 +1,16 @@
+#############################################################
+#
+# Bluez
+#
+#############################################################
+BLUEZ_VERSION:=4.71
+BLUEZ_SOURCE:=bluez-$(BLUEZ_VERSION).tar.gz
+BLUEZ_SITE:=http://www.kernel.org/pub/linux/bluetooth
+BLUEZ_LIBTOOL_PATCH:=NO
+BLUEZ_INSTALL_STAGING:=NO
+BLUEZ_INSTALL_TARGET:=YES
+BLUEZ_DEPENDENCIES:= dbus-glib
+
+BLUEZ_CONF_OPT:= --enable-tools --disable-static --enable-shared
+
+$(eval $(call AUTOTARGETS,package,bluez))
--
1.7.0.4
next prev parent reply other threads:[~2010-09-13 15:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-13 15:12 [Buildroot] [PATCH 0/5] add/update packages Chih-Min Chao
2010-09-13 15:12 ` [Buildroot] [PATCH 1/5] iperf : bump to 2.0.5 Chih-Min Chao
2010-09-25 22:35 ` Peter Korsgaard
2010-09-13 15:12 ` [Buildroot] [PATCH 2/5] tiff : bump to 3.9.4 Chih-Min Chao
2010-09-25 22:38 ` Peter Korsgaard
2010-09-13 15:12 ` [Buildroot] [PATCH 3/5] libopenal : new package Chih-Min Chao
2010-09-13 15:12 ` Chih-Min Chao [this message]
2010-09-13 15:12 ` [Buildroot] [PATCH 5/5] dbus : bump to 1.2.24 Chih-Min Chao
2010-09-25 22:59 ` Peter Korsgaard
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=1284390735-2261-5-git-send-email-cmchao@gmail.com \
--to=cmchao@gmail.com \
--cc=buildroot@busybox.net \
/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