Stupid legal question. If TCC is GPL (rather than lesser GPL) and you link with libtcc, then you would end up with software that was GPL. This may be significant. Additionally, and start-up object files that TCC generates may be considered "linking with tcc".
So ... anyone want to straighten this out? On Fri, Jun 27, 2014 at 9:15 AM, Vincent Lefevre <[email protected]> wrote: > TCC is distributed with a file "COPYING", corresponding to the > Lesser GPL. This is incorrect. Such a file is normally called > "COPYING.LIB", and "COPYING" should contain the GPL. This is > important because some files are distributed under the GPL only: > > il-opcodes.h > lib/libtcc1.c > texi2pod.pl > win32/tools/tiny_impdef.c > > Moreover the fact that there are some source files under the GPL > (il-opcodes.h, lib/libtcc1.c) cannot make TCC a Lesser GPL software > as claimed by the README file. > > -- > Vincent Lefèvre <[email protected]> - Web: <https://www.vinc17.net/> > 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> > Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon) > > _______________________________________________ > Tinycc-devel mailing list > [email protected] > https://lists.nongnu.org/mailman/listinfo/tinycc-devel >
_______________________________________________ Tinycc-devel mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/tinycc-devel
