Re: [Bluez-devel] Windows Port

["Antony C. Roberts" <acr@acroberts.com>]

Marcel Holtmann wrote:

>Hi Antony,
>
>  
>
>>Thanks for the warning. The stuff I want to port will be isolated in the 
>>services provided and all the code in this application will, as 
>>required, still be GPL. However, the parts which interface to these 
>>services (the hardware driver and the API) would be a modified GPL that 
>>does not require the entire program to be made public but only the 
>>original source code and any modifications made to it.
>>    
>>
>
>if a program contains one line GPL code, the complete source code must
>be available. If you link a library under GPL, the final program will
>also be GPL.
>  
>
True. In this respect the program would be the l2cap and rfcomm 
services. The UI stuff and the driver are separate programs, which don't 
contain any GLP'ed code. If the interfaces to RFCOMM and L2CAP are 
socket based (or pipe based or whatever), then you don't need to link 
with any GPL'ed libs.

That's my thinking. My intention is not to "misuse" GPL'ed code. My 
intention is to give people something that they can innovate with 
commercially. I believe this is good for Bluetooth. It's important for 
Bluetooth that it gets a truely intuitive presence on Windows. Let's not 
turn this discussion into a GPL/non-GPL argument, though.

Besides, I don't even yet know whether or not I am going to heed your 
warnings and implement without using the BlueZ sources. The first step 
is to get the USB driver working and being able to initiate basic HCI 
stuff - that will be a completely new implementation and nothing to do 
with BlueZ. Once I've gotten there, I'll make a definite decision.

Regards,
Antony C. Roberts.