[Libav-user] Question about the libraries' naming and rule #16

Alex Cohn alexcohn at netvision.net.il
Tue Jun 7 17:30:10 CEST 2011

Kirill, it's no cheating to link all libav* static libraries
(including swscale) into single dynamic library. That's exactly what
rockplayer did for Android. It is an easy and clean way to avoid LGPL


On Tuesday, June 7, 2011, Kirill Gavrilov <gavr.mail at gmail.com> wrote:
> 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).There NO problem to statically link with LGPL/GPL product (in fact console utility ffmpeg is often statically linked with libav* libraries).
> However for product with other license only option - to use dynamic libraries. You may to cheat - merge all libraries into ONE and publish their sources / build procedures
> over LGPL license however this doesn't make your product friendly for user AND your closed-source product still NEED to build against this dynamic library!
> -----------------------------------------------
> Kirill Gavrilov,Software designer.
>  <kirill at sview.ru>

More information about the Libav-user mailing list