Packetizer Forums

I wanted to reach the author regarding the compatibility issues with H.323 Plus (1.24.0) and older FFmpeg releases (.e.g. 0.7 branch) never mind something fairly new-ish like the 0.10 branch. H.323 Plus is the only project left in the OpenBSD ports tree I'm having issues with trying to build with newer FFmpeg. We've had some minimalist patching to get H.323 Plus to build and run with FFmpeg 0.7 snapshots but as the API has changed even further between 0.7 and 0.8/0.9 and 0.10 snapshots we're using now this is causing further issues trying to build H.323 Plus. I see in the CVS repo you have made some sort of attempt at dealing with this for some parts of H.323 Plus code but then later reverted it. Even with that there was still the issue of fixing the autoconf script as well. Can you comment on when we might see a new release of H.323 Plus that will work with newer FFmpeg releases "out of the box"?

Hi,

I'm compiling the codecs ffrom H323Plus CVS with ffmpeg 0.9 on Linux and that seems to work fine.

Jan

The issue with the autoconf script is the library check for libavcodec...

AC_CHECK_LIB(avcodec, h263p_encoder, [HAVE_H263=yes], [HAVE_H263=no])
AC_CHECK_LIB(avcodec, h263p_encoder, [HAVE_H263P=yes], [HAVE_H263P=no])
AC_CHECK_LIB(avcodec, mpeg4_encoder, [HAVE_MPEG4=yes], [HAVE_MPEG4=no])
AC_CHECK_LIB(avcodec, h264_decoder, [HAVE_H264_DECODER=yes], [HAVE_H264_DECODER=no])

looking for each respective encoder and seeing if the copy of avcodec has been built with the codec.

http://git.videolan.org/?p=ffmpeg.git;a ... 2e32d921d0

relatively modern FFmpeg has renamed the internal encoder/decoder symbols and prefixed them with ff_. So these tests will fail. But for even newer FFmpeg the symbols are not exported.

The ffmpeg version that ships with the distros I use doesn't use the prefix, but if you can supply a patch tested with your version, I'll put it into the CVS.