summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorArmin Kuster <akuster808@gmail.com>2016-01-01 11:42:47 -0800
committerMartin Jansa <Martin.Jansa@gmail.com>2016-01-14 11:22:11 +0100
commitb556364b72dd1600eac2602add0e137daf721adc (patch)
tree725ffb7aadcdc2924bccef0dc4b05d58a46f7e84
parent3c1ad2dcf95e087f30ac747b8702d19b1dd073e2 (diff)
downloadmeta-openembedded-b556364b72dd1600eac2602add0e137daf721adc.tar.gz
fltk: Fix license warning
WARNING: fltk: No generic license file exists for: FLTK in any provider Add license Signed-off-by: Armin Kuster <akuster808@gmail.com>
-rw-r--r--meta-oe/licenses/FLTK43
1 files changed, 43 insertions, 0 deletions
diff --git a/meta-oe/licenses/FLTK b/meta-oe/licenses/FLTK
new file mode 100644
index 000000000..27a32a258
--- /dev/null
+++ b/meta-oe/licenses/FLTK
@@ -0,0 +1,43 @@
1 FLTK License
2 December 11, 2001
3
4The FLTK library and included programs are provided under the terms
5of the GNU Library General Public License (LGPL) with the following
6exceptions:
7
8 1. Modifications to the FLTK configure script, config
9 header file, and makefiles by themselves to support
10 a specific platform do not constitute a modified or
11 derivative work.
12
13 The authors do request that such modifications be
14 contributed to the FLTK project - send all
15 contributions to "fltk-bugs@fltk.org".
16
17 2. Widgets that are subclassed from FLTK widgets do not
18 constitute a derivative work.
19
20 3. Static linking of applications and widgets to the
21 FLTK library does not constitute a derivative work
22 and does not require the author to provide source
23 code for the application or widget, use the shared
24 FLTK libraries, or link their applications or
25 widgets against a user-supplied version of FLTK.
26
27 If you link the application or widget to a modified
28 version of FLTK, then the changes to FLTK must be
29 provided under the terms of the LGPL in sections
30 1, 2, and 4.
31
32 4. You do not have to provide a copy of the FLTK license
33 with programs that are linked to the FLTK library, nor
34 do you have to identify the FLTK license in your
35 program or documentation as required by section 6
36 of the LGPL.
37
38 However, programs must still identify their use of FLTK.
39 The following example statement can be included in user
40 documentation to satisfy this requirement:
41
42 [program/widget] is based in part on the work of
43 the FLTK project (http://www.fltk.org).