Posts: 3,978
Threads: 177
Joined: Apr 2022
Reputation:
220
What is specifically is LGPL in QB64 programs and why does whole source have to be posted if what one Sub or Function is used?
I am not a fan of posting code without source but why should the whole source be necessary? That doesn't sound right to me. Does that include source for all libraries and other includes say from C or C++ or Windows API? eg do I have to source all of Windows too?
Somethings wrong here!
b = b + ...
Posts: 303
Threads: 10
Joined: Apr 2022
Reputation:
44
LGPL is a software license, and basically it says that if code licensed under it is included in your executable then you have to release the source code for the entire thing. So whether you put in an include or etc. doesn't matter, that's still part of the source and would have to be released.
I'm regards to your other question, the requirement ends at system libraries like the windows API. LGPL is also less strict than the GPL and doesn't impose the requirement if the dependency is a dll.
Posts: 303
Threads: 10
Joined: Apr 2022
Reputation:
44
The requirement is placed on your code when it is used with an LGPL library, which your code is if you use sound in your QB64 code.
IE. Your QB64 code is used to make an executable with an LGPL library in it (if you use sound). That means the source for the executable needs to be made available, and that source is your QB64 code.
Posts: 422
Threads: 27
Joined: Apr 2022
Reputation:
26
07-17-2022, 07:37 PM
(This post was last modified: 07-17-2022, 07:41 PM by Jack.)
DSMan, is the sound library available as a dll ?
just realized that anyone wanting to go the dll way would need to use the dll functions and avoid the integrated QB64 sound function that use the library
Posts: 303
Threads: 10
Joined: Apr 2022
Reputation:
44
07-17-2022, 07:45 PM
(This post was last modified: 07-17-2022, 07:46 PM by DSMan195276.)
Probably, certainly they could be made into external libraries if they aren't currently available as one. But QB64 doesn't currently offer a way to compile your program to link it again an external version of a library it uses, so on a practical level most users can't make that happen. I am aware that the LGPL doesn't impose the GPL requirements if you link it externally.
FWIW, the is some work currently in progress on GitHub to replace the LGPL sound libraries. If that happens then this is all mostly a moot point.
