Ketan's summary is correct.  Note that each file includes the corresponding licenses:
glew.h: SGI FSL + BSD
glxew.h: GLX + BSD
wglew.h: BSD
glew.c: BSD
auto/bin/*: GPL 2
You do not have to comply with all three licences.  For example, if you only use glew.h, wglew.h, and glew.c in your application, you only need to comply with the SGI FSL + BSD (basically by not removing the licenses in a source distribution and/or by including the licenses in a binary distribution).
Please let us know if you have more specific questions.
 - Milan
----- Original Message -----
From: Ketan Mehta
To: Jason Harrison ; glew-users@lists.sourceforge.net
Sent: Tuesday, December 05, 2006 8:55 PM
Subject: Re: [glew-users] License for GLEW


I had done the analysis of its licensing.

What I understand is that it is consists of multiple licenses:
1) As it uses glext.h and GL extension spec files which are released
by/under  SGI and GLX
2) Original code from which GLEW is extended or derived was under BSD
3) Perl scripts which parses and generatea glew.h, glew.cpp etc is under GPL 2.

So from usage perspective, if you are not modifying generation scripts
and using glew.h/.cp files or libraries you are fine.

Rest can be confirmed by Milan.


On 12/5/06, Jason Harrison <jason.harrison@brightsidetech.com> wrote:
> Hash: SHA1
> Can someone please clarify the licensing for GLEW?  The web pages say:
> > The source code is licensed under the modified BSD license, the SGI
> > Free Software License B, and the GLX Public License. The automatic
> > code generation scripts are released under the GPL.
> Which license goes where?  Do we use all three licenses (GLX, BSD,
> SGI-B) attribution rules?
> - -Jason

Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
glew-users mailing list