On 06/08/2011 02:24 AM, Hendrik Leppkes wrote: > Hi, > > On Wed, Jun 8, 2011 at 2:19 AM, Soltic Lucas <[email protected]> wrote: >> >> From what you say, I suppose I shouldn't even care for that kind of issue, >> and should statically link my library against FFmpeg, as LGPL is not a >> problem to me. Actually I'm getting a bit lost between those who say it's >> possible, and those who say it's not (easily). >> > > If your code is (L)GPL itself, then you really don't need to worry > about this much. Include the GPL license file, mention that you're > using ffmpeg under the (L)GPL, and link it the way you prefer to. You > should probably mention against which version your program was linked, > and provide any changes you applied to ffmpeg (if any at all).
This is very bad advice, IMO. If you distribute FFmpeg with your application, even if your application is open source, you still have to comply with the LGPL's rules on making the source code and build details available. Even if ffmpeg.org ceases to exist in the future. Or they prune their archives, deleting the specific version you shipped. On top of that, you would be hijacking the download bandwidth of ffmpeg's server to meet another projects' obligations. Phil _______________________________________________ Libav-user mailing list [email protected] http://ffmpeg.org/mailman/listinfo/libav-user
