I need help regarding parallel installtion from sources into /usr/local and via packet manager into /usr tree. I have to patch something on ffmpeg and I must use specific x264 svn versions to produce HD clips with Kdenlive because of a bug and a multithreading issue. So it isn't possible to use binaries from a distributor for producing clips. I've learned that it is necessary to build all from sources to keep full control of all my issues.
Meanwhile I've built all successfully from sources into /usr/local (libx264, ffmpeg svn, mlt0.5.10, Kdenlive0.7.8) and I'll use this to produce my HD clips.
Because of the changes to ffmpeg I was uninstalling itself and all other software who depends on it like VLC.
How is it possible to keep all the binaries from my distributor like VLC, ffmpeg and x264 which are good enough for all other purposes like playback parallel to my frozen producer environment from sources?
I've played around a little bit and there are the following issues/questions:
I get an error while making ffmpeg if libx264 is twice present (/usr/lib a. /usr/local/lib)
(With twice I mean including -devel package). Without -devel no problem.
/home/cs/src/ffmpeg-checkout-2010-09-13/libavcodec/libavcodec.so: undefined reference to `x264_encoder_open_104'
collect2: ld returned 1 exit status
make: *** [ffmpeg_g] Fehler 1
If only one libx264 is pressent, all works fine and ffmpeg is linked against it clean. Here against my own /usr/local build.
ldd /usr/local/bin/ffmpeg | grep x264
libx264.so.104 => /usr/local/lib/libx264.so.104 (0xb6562000)
How can I control this manual while the build?
The build of mlt works fine even if both ffmpegs are installed and with or without -devel package.
I've no idea which ffmpeg or libs is mlt using? /usr or /usr/local? How can I proof and control this?
It seems that I've no problems with Kdenlive, because here I can set the path to melt.
Should I follow something here?