[Libav-user] Question about the libraries' naming and rule #16
soltic.lucas at gmail.com
Tue Jun 7 16:49:26 CEST 2011
Actually I thought rule #2 was to avoid the license 'contamination' and give
clear rules. If FFmpeg's HAS to be linked dynamically, why is it possible to
build static libraries?
The purpose here is to avoid having loads of dlls. Initially I was linking
the static libraries to my own product. But I got issues with Visual Studio
and wanted to give a try with dynamic linking. However I don't want the user
to have to care about 5 dlls when he would actually need only one (and zero
with the initial all-statically-linked-in-my-product setup).
2011/6/7 Phil Turmel <philip at turmel.org>
> Hi Lucas,
> On 06/07/2011 09:47 AM, Soltic Lucas wrote:
> > Hello,
> > On the Legal page is written the following:
> > *16. Do not rename FFmpeg dlls to some obfuscated name, but adding a
> > or prefix is fine (renaming "avcodec.dll" to "MyProgDec.dll" is not fine,
> > but to "avcodec-MyProg.dll" is).*
> > What I would like to do is building a dynamic library from the ffmpeg's
> > static libraries, whose name whould be something like ffmpeg.dll. This is
> > not library renaming as I'm building a new library, but I wanted to be
> > it was ok with FFmpeg's rules.
> Look again at rule #2. If you are using the checklist, use the whole
> checklist. The purpose of rule #2 is to make it easy for your end-user to
> replace the ffmpeg DLLs with ones they compile themself, and use your
> application with the substitutes. If you make a new DLL with your own
> object files mixed with the ffmpeg object files, they won't be able to
> There are other ways to meet the requirements of the LGPL, but they are
> more complicated, and the checklist won't help you. You might even need a
> real lawyer. I am not.
> Libav-user mailing list
> Libav-user at ffmpeg.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Libav-user