On Mon, Nov 10, 2014 at 5:38 AM, Fabian Greffrath <fab...@greffrath.com> wrote: > Hey Julian, > > I've just tested your approach with the faad2 package and it works just > as expected. I'll add the necessary changes to the Debian packaging soon > [tm]. But please note that we are not in a hurry: testing is currently > frozen and I see zero chance that faad2 will get a freeze exception with > a change as intrusive as this. > > BTW, I have decided to put the renamed library into the regular libfaad2 > package. It has a different name and weights only ~250kB. So, you only > need to take care to link your own application against the correct > library name. > > @team: Does anyone remember why we put the 10bit-libx264 into a > subdirectory instead of renaming the library? One has to use LD_PRELOAD > magic, anyway, to use it.
According to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667573#29, setting LD_LIBRARY_PATH would do just fine. According to the buglog, I proposed the idea of shipping a shell wrapper that sets that for you, but it seems I never got around doing is. I have attached the shell wrapper that I had to this email. it seems to even work as expected: ./x264-10bit ldd /usr/bin/x264 | grep libx264.so libx264.so.142 => /usr/lib/x86_64-linux-gnu/x264-10bit/libx264.so.142 (0x00007fd32d4e7000) Julien, Fabian, do you think this would be helpful to have in the x264 package under /usr/bin? -- regards, Reinhard
x264-10bit
Description: Binary data
_______________________________________________ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
