-
-
Notifications
You must be signed in to change notification settings - Fork 15
Expand file tree
/
Copy pathlgpl-2.0-fltk.yml
More file actions
31 lines (31 loc) · 2.17 KB
/
Copy pathlgpl-2.0-fltk.yml
File metadata and controls
31 lines (31 loc) · 2.17 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
key: lgpl-2.0-fltk
is_deprecated: yes
replaced_by:
- fltk-exception-lgpl-2.0
short_name: LGPL 2.0 with FLTK exception
name: LGPL 2.0 with FLTK exception
category: Copyleft Limited
owner: FLTK
homepage_url: http://www.fltk.org/COPYING.php
notes: replaced by fltk-exception-lgpl-2.0
is_exception: yes
text: " FLTK License\n December 11, 2001\n\
\ \nThe FLTK library and included programs are provided under the terms\nof the GNU Library\
\ General Public License (LGPL) with the following\nexceptions:\n \n 1. Modifications to\
\ the FLTK configure script, config\n header file, and makefiles by themselves to support\n\
\ a specific platform do not constitute a modified or\n derivative work.\n \n\
\ The authors do request that such modifications be\n contributed to the FLTK\
\ project - send all\n contributions to \"fltk-bugs@fltk.org\".\n \n 2. Widgets that\
\ are subclassed from FLTK widgets do not\n constitute a derivative work.\n \n 3.\
\ Static linking of applications and widgets to the\n FLTK library does not constitute\
\ a derivative work\n and does not require the author to provide source\n code\
\ for the application or widget, use the shared\n FLTK libraries, or link their applications\
\ or\n widgets against a user-supplied version of FLTK.\n \n If you link the application\
\ or widget to a modified\n version of FLTK, then the changes to FLTK must be\n \
\ provided under the terms of the LGPL in sections\n 1, 2, and 4.\n \n 4. You do\
\ not have to provide a copy of the FLTK license\n with programs that are linked to\
\ the FLTK library, nor\n do you have to identify the FLTK license in your\n program\
\ or documentation as required by section 6\n of the LGPL.\n \n However, programs\
\ must still identify their use of FLTK.\n The following example statement can be included\
\ in user\n documentation to satisfy this requirement:\n \n [program/widget]\
\ is based in part on the work of\n the FLTK project (http://www.fltk.org)."