From: Matthew Leotta <mleotta@le...> - 2008-10-10 18:25:35
I've got a new build on the dashboard (finally a Mac OS X build!).
I decided to run this one with the build of FFMPEG that you are using:
svn -r11322 according to comments in vidl2_ffmpeg_istream_v2.txx. It
compiles, but I get an undefined symbol "_img_convert". This is from
the old deprecated FFMPEG image convert functions still used in vidl
and vidl2_ffmpeg_convert (since I haven't taken them out yet).
Apparently the definitions of these functions are still in the
headers, but they are not implemented in r11322.
Did you have this sort of problem with this version of FFMPEG? Should
I add more #ifdefs to old vidl code so that it only works with old
FFMPEG (I have no plans to update vidl for new FFMPEG)? What is the
status on putting a version of FFMPEG in v3p? I don't want to take
the effort to find the range of FFMPEG versions that work with VXL if
there will be a VXL version of FFMPEG soon anyway.
I'm still working on the whole ffmpeg/v3p thing, so you *not* spending
time on it is good.
I didn't have a problem _img_convert not being defined, but that doesn't
mean that it's not pure luck.
If you could pick a revision of ffmpeg that works, why don't we say for
the moment, that vidl2 only supports that version of ffmpeg, and update
that statement once I get the new ffmpeg under control?
From: Matthew Leotta <matt.leotta@gm...> - 2008-10-10 19:29:49
I think the easiest solution for now is for me to downgrade FFMPEG in
this build to the old version that is considered "stable" by many
Linux distributions. At some point I will still need to put more
#ifdefs in the old vidl code or take the time to update it to use your
v3p version. The old vidl will not go away, even when the vidl2 moves
in to take its place.
On Oct 10, 2008, at 2:32 PM, Amitha Perera wrote:
> I'm still working on the whole ffmpeg/v3p thing, so you *not*
> spending time on it is good.
> I didn't have a problem _img_convert not being defined, but that
> doesn't mean that it's not pure luck.
> If you could pick a revision of ffmpeg that works, why don't we say
> for the moment, that vidl2 only supports that version of ffmpeg, and
> update that statement once I get the new ffmpeg under control?