07-07-2022, 03:57 PM
(07-07-2022, 12:50 PM)James D Jarvis Wrote: I read that and I'm a little confused because to me it reads like it's written for someone that wishes to copy and redistribute QB64 or a derived programming application and I'm not too sure how to properly cite licensing compliance for a something like a game or any other specific application as opposed to a development tool. If I have to include all the source code (for the game) it's not a biggie as anyone who frequents this forum can see I'm not very shy about sharing.
I just want to get it right as I'm willing to let them setup redistribution but I don't want them or someone else to get zapped somewhere down the line.
I agree it is a little confusing, but basically there's two things that have to be considered: The license of the QB64 code (`libqb`) that is used in your compiled program, and the license of the various third-party libraries that we utilize to provide features such as images, sound, and other things.
The QB64 portion that is compiled into your program (`libqb`) is MIT licensed, so there's not really anything to worry about there beyond including the copyright notice in your distributed program.
QB64 is smart enough to avoid compiling in any third-party libraries that you don't actually use, and that's basically what the note at the top of `COPYING.txt` is about. Sound support is provided via an LGPL licensed library, so if your program uses sound then your code has meet the LGPL license requirements and you have to provide your source code when distributing the program (more or less). The other libraries have more permissive licenses, and thus mostly just require a copyright notice to be provided.
Also note that I'm pretty sure the information for `FreeGLUT` is wrong, I'll look into addressing that. Everything I can find indicates FreeGLUT is MIT licensed.