On Fri, Apr 29, 2011 at 1:07 AM, Nigel Stewart <nstewart@...> wrote:
>> I'm wondering under which license the text files used for generating
>> the glew header and c files.
> - I'm not a lawyer.
> - Not the views/opinions/position of my employer.
> - I'm the GLEW maintainer/caretaker at the moment.
> "...GLEW is originally derived from the EXTGL project by Lev Povalahev.
> The source code is licensed under the Modified BSD License, the Mesa 3-D
> License (MIT License), and the Khronos License (MIT License). The
> automatic code generation scripts are released under the GNU GPL...."
> The perl files in auto/bin are clearly marked as GPLv2:
> ## This program is distributed under the terms and conditions of the GNU
> ## General Public License Version 2 as published by the Free Software
> ## Foundation or, at your option, any later version.
>> I have written a program which uses the
>> text file to generate OpenGL bindings to another language then C
>> (DigitalMars D), IANAL but the information on the FSF site say that
>> these files should be licensed under the same license as the source
> Generally I guess that might be so. But the way I interpret the GLEW
> licenses (I'm kind of a caretaker/maintainer here) is that the generation
> scripts are GPL, and the output is BSD/Mesa3D/MIT/Khronos. So the GPL
> would apply to a GLEW-like tool (or fork) written in Perl (auto/bin/* and
> Makefiles) - which would normally be redistributed as source anyway.
> If your toolchain only takes the contents of auto/extensions and auto/core
> as input, I wouldn't expect the GPL to apply there. They're a distillation
> of the OpenGL specification and extensions documents.
Yeah that what it does and my reasoning was the same (even tho it
wasn't as clearly written out as yours). I'm planing on
releasing the reader/toolchain thingy anyways.
The "source" files in this case where the text files in
auto/extensions and auto/core and not the perl files. So they would
have the BSD/Mesa3D/MIT/Khronos license as the text files are either
taken from Khronos or Mesa.
In short my output files should have BSD/Mesa3D/MIT/Khronos. Seems we
are on the same page.
>> Now I didn't look at the scripts/programs when I wrote the converter
>> programs since the text files are trivial to parse. So this only
>> leaves the original text files?
> For that you'd need to go upstream to opengl.org / Khronos.
> An alternative is for you to work directly from the .spec files
> provided by Khronos. (GLEW predates those, I guess)
> Hope it helps.
Thanks for taking the time to write out a answer Nigel.