Hi Lucas, On 06/07/2011 08:19 PM, Soltic Lucas wrote: > > Le 7 juin 2011 à 17:29, Phil Turmel a écrit : >> Admirable intent, but you must make it possible for your users to substitute >> their own compilation of FFmpeg into your application. Dynamic linking is >> the simplest way to satify that requirement of the LGPL. > > What does LGPL exactly says about this point? I'm asking this because users > CAN replace my static FFmpeg's libraries with their own, but they would need > to recompile the library. Thus it's not the simplest way, but it's possible.
http://www.gnu.org/licenses/licenses.html The FFmpeg developers have made a checklist for your convenience. Your original question was about how to follow the checklist. If you want to interpret the LGPL yourself, fine, but read it all, and make sure *you* understand it. If you can't, you'd better get a lawyer. Regardless, you must comply with FFmpeg's license to distribute it. >> Another case: If your app hard-codes a specific codec, and the end-user >> wants a different one, they could modify their personal copy of FFmpeg to >> change codec IDs, and trick your app into using the alternate. That's why >> you are obligated to permit reverse engineering of *your* code. > > I do provide the source code of my library and the script used to build it. > With this script the developer can exactly choose which decoders he/she wants > to enable. If he/she ever wanted to modify the FFmpeg sources he can too. If > he/she ever wanted to change the FFmpeg's version being used, it's possible > too. There is nothing against changing the supported codecs, but at build > time only. Once it's built, it's built. It *sounds* like you are complying with the license. But I have not seen your application code, and I am not a lawyer. Phil _______________________________________________ Libav-user mailing list [email protected] http://ffmpeg.org/mailman/listinfo/libav-user
