Linux bluetooth development
 help / color / mirror / Atom feed
From: Brad Midgley <bmidgley@xmission.com>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Linking to BlueZ from non-GPL code
Date: Wed, 01 Jun 2005 18:14:31 -0600	[thread overview]
Message-ID: <429E4F67.1030104@xmission.com> (raw)
In-Reply-To: <EFCD68F7BFDB06468769D4D9EAAA9387077868B0@scsmsx401.amr.corp.intel.com>

Trevor

I usually try to stay out of this but a technical solution is to write a 
GPL shim that links with -lbluetooth and that you use via APIs across 
which the GPL is not required to hold. Again, talk to your lawyer.

Brad

Pering, Trevor wrote:
> Ok, then it sounds like we (me and the lawyers and you) are all in
> agreement -- what it comes down to is the source of the *.h files.  If
> they come from the kernel (which wouldn't make sense for BlueZ), then
> things would be ok.  However, trying to use BlueZ user-level *.h files
> with not-GPL would not be allowed.  (I'm just reiterating this for the
> benefit of clarity and consensus).
> 
> Cheers,
> 	Trevor
> 
>  
> 
> -----Original Message-----
> From: bluez-users-admin@lists.sourceforge.net
> [mailto:bluez-users-admin@lists.sourceforge.net] On Behalf Of Marcel
> Holtmann
> Sent: Wednesday, June 01, 2005 3:48 PM
> To: bluez-users@lists.sourceforge.net
> Subject: RE: [Bluez-users] Linking to BlueZ from non-GPL code
> 
> Hi Trevor,
> 
> 
>>As for the non-GPL use of the kernel, I was referring to: (from
>>http://www.kernel.org/pub/linux/kernel/COPYING)
>>
>>"NOTE! This copyright does *not* cover user programs that use kernel
>> services by normal system calls - this is merely considered normal
> 
> use
> 
>> of the kernel, and does *not* fall under the heading of "derived
> 
> work".
> 
>> Also note that the GPL below is copyrighted by the Free Software
>> Foundation, but the instance of code that it refers to (the linux
>> kernel) is copyrighted by me and others who actually wrote it."
>>
>>But I'm not sure if by "disagree" you meant disagree with the
>>interpretation, or the intent behind it...  I have been advised by our
>>lawyers that this does allow simple use of *.h files to include kernel
>>constants and things like that -- but would not extend to user-land
>>libraries.
> 
> 
> from my interpretation this is only ok if the include files are under
> LGPL. This is normally done by having extra include files for the
> userspace. Remember that we don't include kernel headers from userspace
> programs. If you include *.h files that are under GPL then your program
> becomes GPL, because you include GPL code. In the case of BlueZ you
> can't include the kernel header files, because they are not compatible.
> So you need to use the *.h files from bluez-libs and these are GPL. This
> means you have to rewrite them from scratch and from my view this is not
> possible, because you will create derived work. However I am not a
> lawyer and if you think (or your lawyer do) you are safe then go ahead,
> but done blame me afterwards that I haven't warned you.
> 
> And btw don't get me wrong. I will try to make the BlueZ library LGPL as
> soon as I got the permission from Qualcomm. Without it we don't really
> need to think or talk about it.
> 
> Regards
> 
> Marcel
> 
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by Yahoo.
> Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
> Search APIs Find out how you can build Yahoo! directly into your own
> Applications - visit
> http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005
> _______________________________________________
> Bluez-users mailing list
> Bluez-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-users
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by Yahoo.
> Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
> Search APIs Find out how you can build Yahoo! directly into your own
> Applications - visit http://developer.yahoo.net/?fr=fad-ysdn-ostg-q22005
> _______________________________________________
> Bluez-users mailing list
> Bluez-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-users


-------------------------------------------------------
This SF.Net email is sponsored by Yahoo.
Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
Search APIs Find out how you can build Yahoo! directly into your own
Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2005-06-02  0:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-01 23:43 [Bluez-users] Linking to BlueZ from non-GPL code Pering, Trevor
2005-06-02  0:14 ` Brad Midgley [this message]
2005-06-02  9:57   ` Marco Trudel
2005-06-02 10:10     ` Marcel Holtmann
2005-06-02  0:19 ` Marcel Holtmann
  -- strict thread matches above, loose matches on Subject: below --
2005-06-01 22:17 Pering, Trevor
2005-06-01 22:48 ` Marcel Holtmann
2005-06-02 10:01 ` Marco Trudel
2005-06-01 21:33 Pering, Trevor
2005-06-01 21:44 ` Marcel Holtmann
2005-06-02  5:01   ` Fredy P
2005-06-02 18:55     ` Nils Faerber

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=429E4F67.1030104@xmission.com \
    --to=bmidgley@xmission.com \
    --cc=bluez-users@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