Re: Can't compile

Hello Alexander,

On Sun, May 24, 2020 at 05:39:03PM +0200, Alexander Strasser wrote:
> On 2020-05-23 17:48 +0900, Masaru Nomiya wrote:
> > In the Message;
> >
> >   Subject    : Re: [MPlayer-users] Can't compile
> >   Message-ID : <[email protected]>
> >   Date & Time: Fri, 22 May 2020 07:06:44 -0400
> >
> > The Wanderer <[email protected]> has written:
> > > On 2020-05-21 at 23:07, Masaru Nomiya wrote:
> > > >
> > > > I tried to compile the svn head, I got the error;
> > > >
> > > > [...]
> > > > In file included from libavcodec/mf_utils.c:25:
> > > > libavcodec/mf_utils.h:22:10: fatal error: windows.h: No such file or directory
> > > >    22 | #include <windows.h>
> > > >       |          ^~~~~~~~~~~
> > > > compilation terminated.
> > [...]
> > > Basically, FFmpeg added a new feature, which (I infer) only works on
> > > Windows, and MPlayer hasn't been updated to support autodetecting or
> > > ignoring it properly.
> >
> > > Reportedly, the MPlayer configure options
> >
> > >  --disable-encoder=AAC_MF --disable-encoder=AC3_MF \
> > >  --disable-encoder=MP3_MF --disable-encoder=H264_MF \
> > >  --disable-encoder=HEVC_MF
> >
> > > serve to manually ignore the new feature and compile anyway. I have not
> > > yet tried them myself.
> > [...]
> Sorry for being a bit late to comment on this and the previous posts.
> 
> I committed a fix yesterday afternoon (european time).

After I read the commit email, I did a recompile of MPlayer on GNU/Linux,
and it worked fine.  But I did not verify if the problem happened for me,
too, before.  I'd suspect the issue to be fixed. :)

Thanks,
Erik
-- 
If you're willing to restrict the flexibility of your approach,
you can almost always do something better.
                        -- John Carmack
_______________________________________________
MPlayer-users mailing list
[email protected]
https://lists.mplayerhq.hu/mailman/listinfo/mplayer-users