Re: [PATCH] configure: fix live555 detection

Alexander Strasser <[email protected]>
Newsgroups gmane.comp.video.mplayer.devel
Message-ID <[email protected]>
Hi!

On 2017-02-09 16:13 +0900, KO Myung-Hun wrote:
> 
> 
> Alexander Strasser wrote:
> > On 2017-01-24 10:36 +0900, KO Myung-Hun wrote:
> >>
> >> Alexander Strasser wrote:
> >>>>
> >>>> Built here, but a
> >>>> stream(rtsp://media.smart-streaming.com/mytest/mp4:BigBuckBunny_175k.mov) is
> >>>> not played.
> >>>
> >>>   It doesn't even compile here. If I am not missing something there will be more
> >>> changes needed in addition to the one line I quoted above. If I am not mistaken
> >>> I think we would need to support the asynchronous API of live555 .
> >>>
> >>
> >> live555 dropped synchronous interface. However, for a while, they
> >> provided a macro for the compatibility. I'm using live.2012.10.16, and
> >> compiled with -DRTSPCLIENT_SYNCHRONOUS_INTERFACE although I didn't check
> >> whether the latest live555 has this macro.
> > 
> > Seems to have been removed in version 2013.10.25 .
> > 
> 
> This patch does not work with the latest live555 ? Otherwise, I want to
> distinguish this patch from synchronous APIs problems.

  I just checked the latest live555 (live.2017.01.26) and it does not
have the RTSPCLIENT_SYNCHRONOUS_INTERFACE compatibility #define .

  As I mentioned above, according to my research in the Debian git, it
was removed in live.2013.10.25 release.

  So I guess it is either implementing the new API or dropping live555
support.

  I could also imagine to accept a patch like yours and have it working
with live555 versions before live.2013.10.25 . Though actually I am not
much in favor of that as it kind of would "promote" using out of date
version of dependencies.


  Alexander
_______________________________________________
MPlayer-dev-eng mailing list
[email protected]
https://lists.mplayerhq.hu/mailman/listinfo/mplayer-dev-eng
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.