From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Using BlueZ
Date: Sun, 10 Dec 2006 20:49:26 +0100 [thread overview]
Message-ID: <1165780166.11292.0.camel@localhost> (raw)
In-Reply-To: <0FA9D595-36DD-4499-92B1-7C7080955B55@mac.com>
Hi Brian,
> >> I would like to know if its possible to use the BlueZ stack with
> >> something that has a GPL incompatible license? i.e. MPL? I noticed
> >> that its GPL licensed which limits its usage with such projects. Any
> >> alternatives?
> >
> > if you have to link against the Bluetooth library, then the answer is
> > no. If you only use the D-Bus interface of BlueZ, then you link
> > against
> > the D-Bus library and this one is LGPL, so that is no problem. However
> > you should always double check with "ldd" what libraries are actually
> > linked in or if you include header files from "bluetooth/*.h". Make
> > sure
> > you don't link against the Bluetooth library and you are good.
>
> Do you loose any functionality vis D-Bus?
depends on what you need to do. Describe your use case and I might be
able to tell you.
Regards
Marcel
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-12-10 19:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-08 16:32 [Bluez-devel] Using BlueZ Brian West
2006-12-10 12:33 ` Marcel Holtmann
2006-12-10 19:03 ` Brian West
2006-12-10 19:49 ` Marcel Holtmann [this message]
2006-12-10 19:52 ` Brian West
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=1165780166.11292.0.camel@localhost \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.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 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.