[MPlayer-dev-eng] Adapt config.h's generation with some ffmpeg's commits

Alexander Strasser eclipse7 at gmx.net
Fri Jan 5 23:47:06 EET 2018

Hi Nicolas!

On 2018-01-04 23:36 +0100, Nicolas George wrote:
> Alexander Strasser (2018-01-04):
> > I am currently working on AVX512 myself, because it for sure 
> > breaks the build (for internal FFmpeg).
> Is there something severe preventing from just calling FFmpeg's
> configure?

Nothing severe AFAICT.

It's just that all the little bits are adding up, making it
really hard to find a way to go that's not too cumbersome.

Please note that above is only an assumption because AFAIK there
is likely nobody that has the complete knowledge of the problem.

> IIUC, the only difference is that we want autodetection for a few
> external libraries. That could probably be arranged.

I fear it's not that simple :(

I have been wanting to improve the state of the build system
for a few years now. I still haven't managed to come up with a
precise plan that is obviously an improvement and would
predictably be not too much work.

I fully agree that we should change something. It feels like the
configure fixes we need to implement because of the way we embed
internal FFmpeg are way too costly. Personally I have the impression
those pure maintenance commits are hindering me from doing actual
MPlayer development.

OTOH I think we should look at some VCS data, because feelings are
feelings. I will open a new discussion thread for that. Hopefully
including a patch that will ease maintenance by running FFmpeg's
configure. Motivated by your comment, I have tried to implement that
and it looks promising so far.

The mentioned patch could make your patch obsolete. So it's probably
better to not invest more work into it like I originally suggested.

Best regards,

More information about the MPlayer-dev-eng mailing list