From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Cc: bluez-devel@lists.sf.net
Subject: Re: [Bluez-devel] Bluez without libbluez?
Date: Sun, 17 Jul 2005 15:39:37 +0200 [thread overview]
Message-ID: <1121607577.22662.16.camel@pegasus> (raw)
In-Reply-To: <1121456287.7374.16.camel@gandalf.tm.informatik.uni-frankfurt.de>
Hi Mickey,
> Is there anyone who wrote a library or application using the Bluez
> kernel layer without linking to libbluez out there? I have been starting
> to write a C++ wrapper as part of a library that's supposed to be
> licensed under LGPL which means I can't look nor link nor even take part
> of the code of libbluez (which is GPL).
>
> However, I didn't find any documentation that does teaches how to do
> that.
and how do you think it is possible to write a library that uses a
kernel interface that is under GPL. We have the bdaddr_t and some other
socket structs that you need to copy. However ask a lawyer about these
legal things.
And btw the Bluetooth library will be re-released under LGPL if I get an
approval from Qualcomm.
Regards
Marcel
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2005-07-17 13:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-15 19:38 [Bluez-devel] Bluez without libbluez? Michael 'Mickey' Lauer
2005-07-15 22:26 ` Fred Schaettgen
2005-07-17 13:39 ` Marcel Holtmann [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=1121607577.22662.16.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sf.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox