On Wed, 2005-07-27 at 11:29 -0400, Dan Dennedy wrote:
> I don't know of any other solution. Why are you so concerned about ABI at this
> point? It's not like there are many users or widespread distribution.
General point of interest - have been focusing on ABI for a long time
and haven't broke it for a while.
> ones who would be affected are already running off CVS HEAD and need to be
> willing to rebuild things if willing to do CVS updates, update FFMPEG from
> CVS routinely, etc.
Well, yes, but I still don't want to be forced to recompile everything
that links to the libs just because I do an update, nor do I like
finding odd behaviour simply because I've forgotten to do so...
Thing is that I'm unsure of precisely what the problem is here - mlt and
mlt++ compiled, and swig broke. That seems to point to a problem with
the swig generated code doesn't it? AFAICT, there's nothing wrong with
the original code..