summaryrefslogtreecommitdiff
path: root/libopie2/opiebluez/config.in
authormickeyl <mickeyl>2005-07-10 18:23:38 (UTC)
committer mickeyl <mickeyl>2005-07-10 18:23:38 (UTC)
commit71fc7a0b9722b1a9695049f2885d5247449fbd6c (patch) (side-by-side diff)
tree4006dff6f7333e72156426b7740a5ea725accc3a /libopie2/opiebluez/config.in
parent779359497a582d510da0448f41a14e44db6b52af (diff)
downloadopie-71fc7a0b9722b1a9695049f2885d5247449fbd6c.zip
opie-71fc7a0b9722b1a9695049f2885d5247449fbd6c.tar.gz
opie-71fc7a0b9722b1a9695049f2885d5247449fbd6c.tar.bz2
s/opieshower/opiebluez/, infrared better goes through opienet
there's the need of a connection abstraction library which bases on opienet and opiebluez in the future. It's for discussion if it makes sense in Opie 1.x
Diffstat (limited to 'libopie2/opiebluez/config.in') (more/less context) (ignore whitespace changes)
-rw-r--r--libopie2/opiebluez/config.in7
1 files changed, 7 insertions, 0 deletions
diff --git a/libopie2/opiebluez/config.in b/libopie2/opiebluez/config.in
new file mode 100644
index 0000000..502181b
--- a/dev/null
+++ b/libopie2/opiebluez/config.in
@@ -0,0 +1,7 @@
+ config LIBOPIE2BLUEZ
+ boolean "libopie2bluez (Linux Bluetooth subsystem BlueZ related classes)"
+ default "y"
+ depends ( LIBQPE || LIBQPE-X11 ) && LIBOPIE2CORE && LIBBLUEZ_DEP
+ comment "libopie2net needs a libqpe, libopie2core, and libbluez"
+ depends !(( LIBQPE || LIBQPE-X11 ) && LIBOPIE2CORE && LIBBLUEZ_DEP)
+