If I write software that uses the rtlsdr library that is already installed on the computer, does my software also have to be opensource?
Thanks, Richard
Richard Frye richard@codingstudios.com writes:
If I write software that uses the rtlsdr library that is already installed on the computer, does my software also have to be opensource?
IANAL, TINLA.
rtl-sdr and osmo-sdr both appear to be GNU GPLv2.
The standard interpretation is that if you create a derived work by writing a program that uses those libraries, then distributing that derived work requires permission from the copyright holders of the used libraries. And, that permission is only available if you license your work under the same license, GPLv2. That is the point of the license.
If you want to write software and not distribute it at all, that's another matter, and the standard interpetation is that this is ok.
What are you trying to write, and what are you thinking about for licensing, other than GPLv2?
I want to write a program that is for sale without releasing all of the source code. Some of it is fine but parts are proprietary. Does it matter if I dynamically link the rtlsdr library?
-Richard
On Mon, Apr 15, 2019, 8:45 PM Greg Troxel gdt@lexort.com wrote:
Richard Frye richard@codingstudios.com writes:
If I write software that uses the rtlsdr library that is already
installed
on the computer, does my software also have to be opensource?
IANAL, TINLA.
rtl-sdr and osmo-sdr both appear to be GNU GPLv2.
The standard interpretation is that if you create a derived work by writing a program that uses those libraries, then distributing that derived work requires permission from the copyright holders of the used libraries. And, that permission is only available if you license your work under the same license, GPLv2. That is the point of the license.
If you want to write software and not distribute it at all, that's another matter, and the standard interpetation is that this is ok.
What are you trying to write, and what are you thinking about for licensing, other than GPLv2?
Not a lawyer, caveats abound, and all that, but;
Excerpt from GPL's licence FAQ:
*The program dynamically links plug-ins, and they make function calls to each other and share data structures, we believe they form a single program, which must be treated as an extension of both the main program and the plug-ins. This means that combination of the GPL-covered plug-in with the non-free main program would violate the GPL.*
So, it sounds like either way you're likely to need to release under GPL or find a different library.
http://www.gnu.org/licenses/gpl-faq.html#IfInterpreterIsGPL
On Tue, Apr 16, 2019, 07:36 Richard Frye richard@codingstudios.com wrote:
I want to write a program that is for sale without releasing all of the source code. Some of it is fine but parts are proprietary. Does it matter if I dynamically link the rtlsdr library?
-Richard
On Mon, Apr 15, 2019, 8:45 PM Greg Troxel gdt@lexort.com wrote:
Richard Frye richard@codingstudios.com writes:
If I write software that uses the rtlsdr library that is already
installed
on the computer, does my software also have to be opensource?
IANAL, TINLA.
rtl-sdr and osmo-sdr both appear to be GNU GPLv2.
The standard interpretation is that if you create a derived work by writing a program that uses those libraries, then distributing that derived work requires permission from the copyright holders of the used libraries. And, that permission is only available if you license your work under the same license, GPLv2. That is the point of the license.
If you want to write software and not distribute it at all, that's another matter, and the standard interpetation is that this is ok.
What are you trying to write, and what are you thinking about for licensing, other than GPLv2?
That is what I thought but I wanted to double check. Thanks for the help.
-Richard
On Tue, Apr 16, 2019, 8:55 AM Tom Swartz tom@tswartz.net wrote:
Not a lawyer, caveats abound, and all that, but;
Excerpt from GPL's licence FAQ:
*The program dynamically links plug-ins, and they make function calls to each other and share data structures, we believe they form a single program, which must be treated as an extension of both the main program and the plug-ins. This means that combination of the GPL-covered plug-in with the non-free main program would violate the GPL.*
So, it sounds like either way you're likely to need to release under GPL or find a different library.
http://www.gnu.org/licenses/gpl-faq.html#IfInterpreterIsGPL
On Tue, Apr 16, 2019, 07:36 Richard Frye richard@codingstudios.com wrote:
I want to write a program that is for sale without releasing all of the source code. Some of it is fine but parts are proprietary. Does it matter if I dynamically link the rtlsdr library?
-Richard
On Mon, Apr 15, 2019, 8:45 PM Greg Troxel gdt@lexort.com wrote:
Richard Frye richard@codingstudios.com writes:
If I write software that uses the rtlsdr library that is already
installed
on the computer, does my software also have to be opensource?
IANAL, TINLA.
rtl-sdr and osmo-sdr both appear to be GNU GPLv2.
The standard interpretation is that if you create a derived work by writing a program that uses those libraries, then distributing that derived work requires permission from the copyright holders of the used libraries. And, that permission is only available if you license your work under the same license, GPLv2. That is the point of the license.
If you want to write software and not distribute it at all, that's another matter, and the standard interpetation is that this is ok.
What are you trying to write, and what are you thinking about for licensing, other than GPLv2?
Just because this is being brought up. Does this mean you can use a GPL compatible license and must use GPL?
Sent from my iPad
On Apr 16, 2019, at 6:50 AM, Tom Swartz tom@tswartz.net wrote:
Not a lawyer, caveats abound, and all that, but;
Excerpt from GPL's licence FAQ:
The program dynamically links plug-ins, and they make function calls to each other and share data structures, we believe they form a single program, which must be treated as an extension of both the main program and the plug-ins. This means that combination of the GPL-covered plug-in with the non-free main program would violate the GPL.
So, it sounds like either way you're likely to need to release under GPL or find a different library.
http://www.gnu.org/licenses/gpl-faq.html#IfInterpreterIsGPL
On Tue, Apr 16, 2019, 07:36 Richard Frye richard@codingstudios.com wrote: I want to write a program that is for sale without releasing all of the source code. Some of it is fine but parts are proprietary. Does it matter if I dynamically link the rtlsdr library?
-Richard
On Mon, Apr 15, 2019, 8:45 PM Greg Troxel gdt@lexort.com wrote: Richard Frye richard@codingstudios.com writes:
If I write software that uses the rtlsdr library that is already installed on the computer, does my software also have to be opensource?
IANAL, TINLA.
rtl-sdr and osmo-sdr both appear to be GNU GPLv2.
The standard interpretation is that if you create a derived work by writing a program that uses those libraries, then distributing that derived work requires permission from the copyright holders of the used libraries. And, that permission is only available if you license your work under the same license, GPLv2. That is the point of the license.
If you want to write software and not distribute it at all, that's another matter, and the standard interpetation is that this is ok.
What are you trying to write, and what are you thinking about for licensing, other than GPLv2?
I am, too, not a lawyer, but: The GPL is meant to ensure exactly what you plan to do doesn't happen: If you distribute a program based on librtlsdr, the person receiving your software has a right to its source code. Dynamically linking usually doesn't change that fact; that's interaction directly between machine code through shared state/memory.
Best regards, Marcus
On Tue, 2019-04-16 at 07:36 -0400, Richard Frye wrote:
I want to write a program that is for sale without releasing all of the source code. Some of it is fine but parts are proprietary. Does it matter if I dynamically link the rtlsdr library?
-Richard
On Mon, Apr 15, 2019, 8:45 PM Greg Troxel gdt@lexort.com wrote:
Richard Frye richard@codingstudios.com writes:
If I write software that uses the rtlsdr library that is already installed on the computer, does my software also have to be opensource?
IANAL, TINLA.
rtl-sdr and osmo-sdr both appear to be GNU GPLv2.
The standard interpretation is that if you create a derived work by writing a program that uses those libraries, then distributing that derived work requires permission from the copyright holders of the used libraries. And, that permission is only available if you license your work under the same license, GPLv2. That is the point of the license.
If you want to write software and not distribute it at all, that's another matter, and the standard interpetation is that this is ok.
What are you trying to write, and what are you thinking about for licensing, other than GPLv2?
See : https://www.gnu.org/licenses/gpl-faq.html#IfLibraryIsGPL
which deal explicitely with this case.
On Tue, Apr 16, 2019 at 2:25 PM Sylvain Munaut 246tnt@gmail.com wrote:
I want to write a program that is for sale without releasing all of the source code. Some of it is fine but parts are proprietary. Does it matter if I dynamically link the rtlsdr library?
It doesn't matter.
Cheers,
Sylvain
Yes if you want to distribute it needs to be with a GPL compatible license.
On Tue, Apr 16, 2019 at 2:35 AM Richard Frye richard@codingstudios.com wrote:
If I write software that uses the rtlsdr library that is already installed on the computer, does my software also have to be opensource?
Thanks, Richard
Hello Richard,
have a look at rtl_tcp.
You would need users to run rtl_tcp and then you should be able to get the data from the network with your own proprietary software.
I have no experience with rtl_tcp, but it it would not do precisely what you want you can modify it and make your modified version available with an opensource license.
As I understand things: Once the data is on your local network it has left the world of open source and you should be free to process it whatever way you want.
Regards
Leif
If I write software that uses the rtlsdr library that is already installed on the computer, does my software also have to be opensource?
Thanks, Richard
Note that bundling any specifically modified version or rtl_tcp would fall under circumvention ...
On Tue, Apr 16, 2019 at 10:11 PM Leif Asbrink leif@sm5bsz.com wrote:
Hello Richard,
have a look at rtl_tcp.
You would need users to run rtl_tcp and then you should be able to get the data from the network with your own proprietary software.
I have no experience with rtl_tcp, but it it would not do precisely what you want you can modify it and make your modified version available with an opensource license.
As I understand things: Once the data is on your local network it has left the world of open source and you should be free to process it whatever way you want.
Regards
Leif
If I write software that uses the rtlsdr library that is already installed on the computer, does my software also have to be opensource?
Thanks, Richard
-
Bill Gaylord -
Greg Troxel -
Leif Asbrink -
Müller, Marcus (CEL) -
Richard Frye -
Sylvain Munaut -
Tom Swartz