In article <[email protected]>, Alexander Terekhov <[email protected]> wrote:
>Right answer: > >Neither static linking nor dynamic linking triggers the GPL infection. If you link against a single .o file that could be called a part of the GPL project, then there could be a problem. If you however link against a separate work (e.g. an independently developed library) you are definitely right. The GPL (v2) is intentionally "open" against this kind of linkage. With the GPLv3 this is different, this is why you need to be extremely careful with GPLv3 projects. The GPLv3 tries to prevent combinations with most libraries. -- EMail:[email protected] (home) Jörg Schilling D-13353 Berlin [email protected] (uni) [email protected] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily _______________________________________________ gnu-misc-discuss mailing list [email protected] http://lists.gnu.org/mailman/listinfo/gnu-misc-discuss
