search

shinchiro / mpv-winbuild-cmake

CMake-based MinGW-w64 Cross Toolchain
658 stars 115 forks source link

[Suggestion] One mpv to rule them all (on windows) #722

Open rubyFeedback opened 6 days ago

rubyFeedback commented 6 days ago

Hey there,

If we go to this page:

https://mpv.io/installation/

It recommends e. g.

Windows builds by shinchiro
Windows builds by zhongfly

And some more.

I am using Linux most of the time, but I do have a mpv.exe for use on Windows. I forgot which one I downloaded it from, and now I am trying to pick the one that I picked before (which I don't remember).

Anyway - do you think it could be possible to streamline this in the long run? Is it necessary that we have multiple different windows binaries for mpv? It may not be under your control what other people do, but perhaps it may help from the downstream-user perspective to consider that we may want to have one-binary-to-rule-them-all e. g. the one that just works, and most devs wanting to provide a binary for windows could all agree on a consensus build. That could be kept in a flexible way to allow for some customization, but built into the same binary; and users could just download this, then. That would reduce confusion too.

At any rate, this is just a suggestion. Please feel free to close this issue at any moment in time and thanks for reading it.

NotTsunami commented 6 days ago

but built into the same binary

There are differences in the libraries included and the build flags used. These are not something you can toggle in runtime. I think there being a choice of different binaries is great. More power for the power users.

rorgoroth commented 6 days ago

Well if they add some meat (features/deps) to the official CI build and add a basic installer/updater nothing by anyone else will be needed, self build is easy if you need something slim, fat or weird.

Shouldn't be too much work at all -- I say that but of course I will not be doing it 🤣