Sam Watkins wrote:
> hi,
>
> my friend asked me to find a public domain or MIT licensed gui library. He
> does not want to have to include license text with his executables /
> packages, apparently the LGPL and GPL require that.
No, you do not have to include GPL or LGPL license
with your executables -- that's just wrong.
Says so at the top of the FLTK LGPL license (emphasis added):
----
4. You *do not* have to provide a copy of the FLTK license
with programs that are linked to the FLTK library, *nor*
do you have to identify the FLTK license in your
program or documentation as required by section 6
of the LGPL.
----
The only thing FLTK asks of your binary releases is:
----
However, programs must still identify their use of FLTK.
The following example statement can be included in user
documentation to satisfy this requirement:
[program/widget] is based in part on the work of
the FLTK project (http://www.fltk.org).
----
You only need to include the license if you include fltk's
source code with your app. ie. if you include FLTK's source,
do not strip out the license files or copyright notices..
which kind of goes without saying.
Your binaries can be released anyway you want.. public
domain, commercially paid for, licensed, or confidential,
whatever.
> This page http://www.hal9k.com/cug/links/subject35.htm says that fltk was
> once public domain, but now it is LGPL.
>
> Can some one tell me what version of the FLTK library is public domain, if it
> is any good, and where I can get it?
Hmm, I know of no such release of FLTK.
I would not go by that info.
If there was one, it's surely so dated as to be irrelevant,
(ie. before FLTK was ported to multiple platforms)
and likely would not compile on modern operating systems.
_______________________________________________
fltk-dev mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk-dev
