[FFmpeg-user] Specifying lib path when building ffmpeg

[Sven C. Dack]

On 03/11/16 18:34, Matteo Naccari wrote:
> Dear FFmpeg users,
>
> I'm trying to build a fork of ffmpeg under Linux (Ubuntu 14.04, gcc 4.82) which then integrates the codec I'm working on (https://github.com/bbc/turingcodec). This codec uses some boost libraries which ship with the source code. However, when I build ffmpeg enabling the Turing codec (--enable-libturing) I can see that the executable of ffmpeg links the system's boost libraries. Is there a way to link to the libraries associated with the Turing codec? I've tried the --extra-ldflags option but no joy. The way I configure the build is the following:
>
> PATH="/path/to/source/code/bin:$PATH" PKG_CONFIG_PATH="$HOME/ffmpeg_build/lib/pkgconfig" ./configure --prefix="$HOME/ffmpeg_build" --pkg-config-flags="--static" --extra-cflags="-I$HOME/ffmpeg_build/include" --extra-ldflags="-L$HOME/ffmpeg_build/lib-L/path/to/turing/source/code/build/release/boost" --bindir="$HOME/bin" --enable-gpl --enable-nonfree --enable-libturing
>
> Many thanks for your help!
> Best regards,
> Matteo
>

The line with:

--extra-ldflags="-L$HOME/ffmpeg_build/lib-L/path/to/turing/source/code/build/release/boost"

should say:

--extra-ldflags="-L$HOME/ffmpeg_build/lib -L/path/to/turing/source/code/build/release/boost"

It's missing a blank between the two -L<path> arguments.