[FFmpeg-devel] [PATCH] faq: explain dependency problems with static libs.

Clément Bœsch ubitux at gmail.com
Wed Jul 11 15:24:53 CEST 2012


On Wed, Jul 11, 2012 at 12:43:09PM +0200, Michael Niedermayer wrote:
> On Wed, Jul 11, 2012 at 12:02:33PM +0200, Nicolas George wrote:
> > 
> > Signed-off-by: Nicolas George <nicolas.george at normalesup.org>
> > ---
> >  doc/faq.texi |   11 +++++++++++
> >  1 file changed, 11 insertions(+)
> > 
> > diff --git a/doc/faq.texi b/doc/faq.texi
> > index da44adb..f9e0be0 100644
> > --- a/doc/faq.texi
> > +++ b/doc/faq.texi
> > @@ -383,6 +383,17 @@ Yes, as long as the code is optional and can easily and cleanly be placed
> >  under #if CONFIG_GPL without breaking anything. So, for example, a new codec
> >  or filter would be OK under GPL while a bug fix to LGPL code would not.
> >  
> > + at section I'm using FFmpeg from within my C application but the linker complains about missing symbols from the libraries themselves.
> > +
> > +FFmpeg builds static libraries by default. In static libraries, dependencies
> > +are not handled. That has two consequences. First, you must specify the
> > +libraries in dependency order: @code{-lavdevice} must come before
> > + at code{-lavformat}, @code{-lavutil} must come after everything else, etc.
> > +Second, external libraries that are used in FFmpeg have to be specified too.
> > +
> > +The easy way to get the full list of required libraries in dependency order
> > +is to use @code{pkg-config}.
> 
> maybe an example gcc command line with pkg-config could be added
> 

Or maybe point to $SHARE/examples/Makefile?

[...]

-- 
Clément B.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 490 bytes
Desc: not available
URL: <http://ffmpeg.org/pipermail/ffmpeg-devel/attachments/20120711/4b030864/attachment.asc>


More information about the ffmpeg-devel mailing list