Hi Ivan, On 11.08.2014 01:23, Ivan Kalvachev wrote:
The patch is inspired by something I read in the Debian discussion. Libav and FFmpeg could be installed side by side without conflicts in the libraries, thanks to using additional suffixes.
Thanks for your interest in the matter.
However development/include files are still conflicting, so I thought of a simple configure hack to give more control to FFmpeg. With this patch you can do `./configure --extra-incdir="/ffmpeg" ` , as result the header files would be installed in "/usr/local/include/ffmpeg" e.g. "/usr/local/include/ffmpeg/libavcodec/avcodec.h" ...
Assuming it would be possible to install development packages for both at the same time, which one should be used, when building a program?
The change is reflected in the pkgconfig files too. Since applications that link to libraries with addition suffixes should be using pkgconfig, they would be using the correct header includes automatically.
If that's to be determined via pkg-config files, then the obvious problem is that both install these files in the same location, and if one doesn't, programs can't find the library.
I did just a rudimentary test and I couldn't spot anything wrong. Please test it before inclusion.
The patch seems to be alright, but it doesn't make it possible to make the development packages of FFmpeg and Libav co-installable.
As for the future, it might be good idea next major release (e.g. 3.0) to have the $prefix/include/ffmpeg as default include path (for non-comapt build).
So this would also not help. Best regards, Andreas _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
