Make it possible to run ffmpeg binaries from the source tree

[Artem S. Tashkinov]

Currently there are just two ways of testing FFmpeg builds: either you have to make install or you have to use LD_LIBRARY_PATH. They are both inconvenient.

Please, provide wrappers which will use inplace currently built libraries. This will greatly simplify FFMpeg testing.

[Carl Eugen Hoyos]

I never install and always run the FFmpeg binaries from the source tree without any issues: Please elaborate!

[Artem S. Tashkinov]

Replying to cehoyos:

I never install and always run the FFmpeg binaries from the source tree without any issues: Please elaborate!

Well, ldd ./ffmpeg shows that it uses(links to) system installed libraries.

[Carl Eugen Hoyos]

As said, I never install and always run FFmpeg binaries from the source tree without an issue.
Please explain how I can reproduce the problem you see.

[Hendrik]

If you want to test in-place, maybe just build static instead of shared?

[Artem S. Tashkinov]

Replying to heleppkes:

If you want to test in-place, maybe just build static instead of shared?

I'll write a wrapper myself a tad later and send you a patch. Meanwhile let's close this bug report.

[Artem S. Tashkinov]

Gotta reopen this one:

$ ./configure --enable-static && make
$ ./ffmpeg
./ffmpeg: error while loading shared libraries: libavdevice.so.56: cannot open shared object file: No such file or directory

$ ldd ffmpeg
        linux-gate.so.1 =>  (0xb773e000)
        libavdevice.so.56 => not found
        libavfilter.so.5 => not found
        libavformat.so.56 => not found
        libavcodec.so.56 => not found
        libpostproc.so.53 => not found
        libswresample.so.1 => not found
        libswscale.so.3 => not found
        libavutil.so.54 => not found

FFmpeg is unusable unless it's installed.

[Artem S. Tashkinov]

My bad, I needed to make distclean first.