Le sextidi 6 frimaire, an CCXXIII, Hendrik Leppkes a écrit : > Thats just wrong. There is not one line of proprietary/non-free code that > gets included or linked in libavcodec.
(IANAL) I do not think it works that way. You could apply the same reasoning when linking a proprietary software with a GPL shared library and deduce that it is ok to distribute the resulting binary: this is not the usual doctrine. For things to make sense, I believe you have to consider that the assembly code for a function call is a mix between the source code for the function call and the function prototype; therefore, the license for the prototype applies. (For linking, just copying the SONAME from the library to the binary is probably not enough to elicit copyright; I do not know what happens exactly with symbols versioning.) > Additionally, the API in use is part of the GPU driver, which I would > strongly consider to be a system library (if a driver is not "system", what > is?), and as such falls under the system library exemption in any case. This one looks valid to me. It only covers the GPL side of the question though. Regards, -- Nicolas George
signature.asc
Description: Digital signature
_______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
