On Mon, 5 Jun 2006 14:23:49 +0000 (UTC) [EMAIL PROTECTED] (Frederick Bruckman) wrote:
[...] > 3) The soname changes were all about choosing 1.1-beta(s) while > Xvid 1.0 was still installed, but with an eye toward future ABI > changes in the Xvid shared library. Know that xvidcore's install > target doesn't actually fix up the ELF symlinks, but I do, and > third party packagers could, so we should be prepared for all > possibilities. Please indulge the semi-cosmetic changes -- it was > much easier to copy and paste with the elements on seperate lines. We're recently switched to standard linkage for xvidcore instead dlopen()ing it. We don't have any known legal issues (xvidcore and transcode are both GPL) not clear technical reasons for keep on going with dynamic linkage. Moreover ABI/API changes are ortoghonal to used linkage. So far our thoughts, what you think about (I'm interested in particular in linkage/ABI issues). > 4) The point is to play around with the new vbv_ capabilities. [...] That's pretty interesting. I'll update xvid module ASAP. > 5) The new "xvid4.h" is straight from Xvid. 1.1.0 will use system-provided xvid.h header, so we don't need no more private xvid4.h header. [...] One last (important) thing: If you're interested or you just like in hacking transcode's xvid modules, don't hesitate to post and/or send patches or comments, none of them will be ignored (by maybe answer will come with some delay ;) ). Best regards, -- Francesco Romani - Ikitt ['people always complain, no matther what you do'] IM contact: (email-me, I have antispam default deny!) icq://27-83-87-867 some known bugs: http://www.transcoding.org/cgi-bin/transcode?Bug_Showcase
