|
From: Philipp K. K. <pk...@sp...> - 2006-06-26 19:41:26
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jesus Calvino-Fraga wrote: > Out of the 128 C source files in the device/lib directory, > only 12 are not LGPL I do not know what the intended consequences of the licensing are. AFAIK the real consequences are: LGPL means: Along with each program compiled with sdcc object files or source files have to be shipped and a copy of the LGPL. GPL means: Along with each program compiled with sdcc source files have to be shipped and a copy of the GPL. LGPL or LGPL with linking exception means: No additional requirements on programs compiled with sdcc. In the discussion one and a half month ago it seemed as if developers wanted to impose no restrictions on programs compiled with sdcc. Since for all the targets sdcc supports non-free compilers are available this would make sense, since it will make more people use sdcc (which would otherwise just choose the non-free compilers). If for a target there were non non-free compilers using the LGPL or the GPL would make sense since it would give developers of free software an advantage over developers of nonfree software. The reasoning in the paragraph above is based on analogy to the GNU guidelines of choosing GPL versus LGPL. Philipp -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEoDhZbtUV+xsoLpoRAnp1AJ9Ovpttay8/Y3gYkH6bmBp4OR5gPgCcCmDf HF7xbcWeZLQAKiMZDshSVt0= =4GP7 -----END PGP SIGNATURE----- |