Re: [Ekiga-devel-list] Challenges for generation of Ekiga 4.x

[Eugen Dedu <Eugen Dedu pu-pm univ-fcomte fr>]

On 01/02/13 08:59, Julien Puydt wrote:
> Le 01/02/2013 08:56, Markus Elfring a Ãcrit :
> > > Those symbols are supposed to come from ffmpeg.
> >
> > I know that ... ;-)
> > https://sourceforge.net/tracker/?func=detail&atid=989748&aid=3602510&group_id=204472
> >
> >
> > When I can not change the reused source files directly, I'll have to
> > extend/adapt my build environment, won't I?
> >
> > Is another developers game "dependency hell" going on here?
> >
> > Which corresponding source file versions should I try to reactivate?
>
> ffmpeg keeps on making incompatible changes to their api ; that is the
> reason why opal's sources contain a known-compatible version : just let
> opal use those sources, and things will go smoothly.

Opal does not have sources of ffmpeg, as far as I know, but only some 
#define to make it compile with several versions of ffmpeg.

The simplest solution I see is that you configure with --disable-h264 
--disable-h263, does this fit your needs?

A better solution is to backport the recent relevant changes from trunk 
to v10.

--
Eugen